summaryrefslogtreecommitdiff
path: root/3 Resources/Linux/Device mapper.md
diff options
context:
space:
mode:
authorJasper Ras <jras@hostnet.nl>2025-03-20 11:07:49 +0100
committerJasper Ras <jras@hostnet.nl>2025-03-20 11:07:49 +0100
commit80ccf68f55dbb70d7e5ed52ee95b3c9d1b6ce264 (patch)
tree93e28e85ab70052aa6f577998ec7dc1f413b40c0 /3 Resources/Linux/Device mapper.md
parent9642cd7ae24f0ba79ce5647c709b35ae8f06a285 (diff)
vault backup: 2025-03-20 11:07:48
Diffstat (limited to '3 Resources/Linux/Device mapper.md')
-rw-r--r--3 Resources/Linux/Device mapper.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/3 Resources/Linux/Device mapper.md b/3 Resources/Linux/Device mapper.md
index 059a0d1..27980ca 100644
--- a/3 Resources/Linux/Device mapper.md
+++ b/3 Resources/Linux/Device mapper.md
@@ -4,7 +4,6 @@
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?
-[[1 projects/Inwerken Mohammed/TODO]]
What is its function in relation to multipath?
Logical devices using device-mapper can be managed using `man 8 dmsetup`