summaryrefslogtreecommitdiff
path: root/3 resources/linux/device-mapper.md
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-01-13 13:16:06 +0100
committerJasper Ras <jras@hostnet.nl>2025-01-13 13:16:06 +0100
commit9232b8d817d4cd4122947375156fa2fa1e9fba14 (patch)
treee4feb77f2e508f008b78f722e91488bb9a3f3806 /3 resources/linux/device-mapper.md
parented0753ad224f0c65133bd7a63180257eecd9f5e3 (diff)
vault backup: 2025-01-13 13:16:06
Diffstat (limited to '3 resources/linux/device-mapper.md')
-rw-r--r--3 resources/linux/device-mapper.md25
1 files changed, 0 insertions, 25 deletions
diff --git a/3 resources/linux/device-mapper.md b/3 resources/linux/device-mapper.md
deleted file mode 100644
index f862496..0000000
--- a/3 resources/linux/device-mapper.md
+++ /dev/null
@@ -1,25 +0,0 @@
-Device mapper is a kernel driver to map physical block devices to virtual ones; this means that for example we can have many physical devices be represented by a single virtual one (linear mapping).
-
-How does it work?
-[[TODO]]
-What is its function in relation to multipath?
-
-Logical devices using device-mapper can be managed using `man 8 dmsetup`
-```
-[jasras@n04.compute.vps2-lej1 ~]$ sudo dmsetup info 3600a098038314d736724566a67346538
-Name: 3600a098038314d736724566a67346538
-State: ACTIVE
-Read Ahead: 256
-Tables present: LIVE
-Open count: 1
-Event number: 3
-Major, minor: 253, 12
-Number of targets: 1
-UUID: mpath-3600a098038314d736724566a67346538
-```
-
-If dmsetup cannot remove a device because a process still has it open, but lsof does not show any processes that open it, use `-f` which replaces the device with a fake that rejects all I/O.
-
----
-[device-mapper](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/device_mapper#device_mapper)
-[dmsetup](https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/logical_volume_manager_administration/dmsetup#dmsetup) \ No newline at end of file