Device Mapper Concepts: Difference between revisions
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
{{Internal|Linux Logical Volume Management Concepts|Logical Volume Management Concepts}} | {{Internal|Linux Logical Volume Management Concepts|Logical Volume Management Concepts}} | ||
==/dev/mapper== | |||
The entries in /dev/mapper can be LVM [[Linux_Logical_Volume_Management_Concepts#Logical_Volume_.28LV.29|logical volumes]], [[Dm-crypt#.2Fdev.2Fmapper|dm-crypt encrypted volumes]], etc. | |||
=RAID= | =RAID= | ||
{{Internal|RAID Concepts|RAID Concepts}} | {{Internal|RAID Concepts|RAID Concepts}} | ||
=Device Mapper Operations= | =Device Mapper Operations= | ||
{{Internal|Device Mapper Operations|Device Mapper Operations}} | {{Internal|Device Mapper Operations|Device Mapper Operations}} | ||
Latest revision as of 08:53, 24 December 2018
Internal
Overview
Device Mapper is a kernel-based framework for volume management. It maps physical block devices onto higher level virtual block devices. Device mapper also offers file system snapshots and thin provisioning. The device mapper framework is the foundation of logical volume manager (LVM), software RAIDs, dm-crypt disk encryption and Docker device-mapper storage backend
Encryption
Logical Volume Management
/dev/mapper
The entries in /dev/mapper can be LVM logical volumes, dm-crypt encrypted volumes, etc.