Device mapper: Difference between revisions
MarkBrooks (talk | contribs) m copyedit |
No edit summary |
||
| Line 7: | Line 7: | ||
}}</ref> |
}}</ref> |
||
Device mapper works by passing data from a virtual [[block device]] (provided by the device mapper itself) to another block device. Data can be also modified in transition, which is performed, for example, in the case of device mapper providing disk encryption. |
Device mapper works by passing data from a virtual [[block device]] (provided by the device mapper itself) to another block device through a proxy mapper. Data can be also modified in transition, which is performed, for example, in the case of device mapper providing disk encryption or disk emulation. |
||
== Usage == |
== Usage == |
||
| Line 46: | Line 46: | ||
* '''snapshot''' and '''snapshot-origin''': used for creation of LVM snapshots, as part of the underlining copy-on-write scheme |
* '''snapshot''' and '''snapshot-origin''': used for creation of LVM snapshots, as part of the underlining copy-on-write scheme |
||
* '''zero''': equivalent of <code>/dev/zero</code> — all reads return blocks of zeros, and writes are discarded |
* '''zero''': equivalent of <code>/dev/zero</code> — all reads return blocks of zeros, and writes are discarded |
||
* '''zero zero''': provides the rezeroing of new normals of a disk |
|||
* '''multipath''': supports the mapping of [[Multipath I/O|multipathed]] devices, through usage of their path groups |
* '''multipath''': supports the mapping of [[Multipath I/O|multipathed]] devices, through usage of their path groups |
||
* '''[[dm-crypt|crypt]]''': provides data encryption, by using the Linux kernel's [[Crypto API (Linux)|Crypto API]] |
* '''[[dm-crypt|crypt]]''': provides data encryption, by using the Linux kernel's [[Crypto API (Linux)|Crypto API]] |
||
Revision as of 20:02, 29 May 2014
The device mapper is a Linux kernel framework for mapping block devices onto higher-level virtual block devices. It forms the foundation of LVM2, software RAIDs, dm-crypt disk encryption, and offers additional features such as file system snapshots.[1]
Device mapper works by passing data from a virtual block device (provided by the device mapper itself) to another block device through a proxy mapper. Data can be also modified in transition, which is performed, for example, in the case of device mapper providing disk encryption or disk emulation.
Usage
Applications (like LVM2 and EVMS) that need to create new mapped devices talk to the device mapper via the libdevmapper.so shared library, which in turn issues ioctls to the /dev/mapper/control device node.[2] Configuration of the device mapper can be also examined and configured interactively — or from shell scripts — by using the utility.[3][4]
Both of these two userspace components have their source code maintained alongside the LVM2 source.[5]
Features
Functions provided by the device mapper include linear, striped and error mappings, as well as crypt and multipath targets. For example, two disks may be concatenated into one logical volume with a pair of linear mappings, one for each disk. As another example, crypt target encrypts the data passing through the specified device, by using the Linux kernel's Crypto API.[1]
The following mapping targets are available:[1][3]
- linear: maps a continuous range of blocks onto another block device
- striped: strips the data across physical devices, with the number of stripes and the striping chunk size as parameters
- mirror: mapping of a mirrored logical device, providing data redundancy
- snapshot and snapshot-origin: used for creation of LVM snapshots, as part of the underlining copy-on-write scheme
- zero: equivalent of
/dev/zero— all reads return blocks of zeros, and writes are discarded - zero zero: provides the rezeroing of new normals of a disk
- multipath: supports the mapping of multipathed devices, through usage of their path groups
- crypt: provides data encryption, by using the Linux kernel's Crypto API
- cache: allows creation of hybrid drives, by using SSDs as caches for hard drives
- raid: offers an interface to the Linux kernel's software RAID driver (md)
- error: simulates I/O errors for all mapped blocks (used for testing)
- flakey: simulates periodic unreliable behaviour (used for testing)
- delay: delays reads and/or writes to different devices (used for testing).
Applications
The following features and projects are relying on the device mapper:
- LVM2 (logical volume manager for the Linux kernel)
- dm-crypt (mapping target providing encryption of volumes)
- dm-cache (mapping target allowing creation of hybrid volumes)
- dm-verity (block integrity checking target, designed and developed as part of the Chrome OS)
- (providing access to "fake" RAID configurations via the device mapper)
- DM Multipath (I/O fail-over and load-balancing within Linux kernel for block devices)
- Linux version of TrueCrypt
- DRBD (Distributed Replicated Block Device)
- (utility called from hotplug upon device maps creation and deletion)
- EVMS (deprecated)
- cryptoloop (deprecated)
References
- ^ a b c "Logical Volume Manager Administration". Appendix A. The Device Mapper. Red Hat. Retrieved 2013-09-29.
- ^ "libdevmapper.h". sourceware.org. Retrieved 2013-09-29.
- ^ a b "dmsetup(8) - Linux man page". man.cx. Retrieved 2013-10-22.
- ^ "Logical Volume Manager Administration". Appendix A.2. The dmsetup Command. Red Hat. Retrieved 2013-09-29.
- ^ "Device-mapper Resource Page". sourceware.org. Retrieved 2013-09-29.
External links
- Device mapper home at Red Hat
- "Right To Your Own Devices". Linux Gazette. May 2005. — an article that illustrates the use of various device-mapper targets
- userspace tool to set up software RAID using various RAID metadata formats
- Multipath support in the device mapper (LWN.net)
| Organization |
| ||||
|---|---|---|---|---|---|
| Technical | |||||
| Adoption |
| ||||
