LVM
The Linux volume-management system that groups physical volumes into volume groups and exposes logical volumes through device-mapper.
Physical volumes (PVs) supply extents to a volume group (VG); application-facing logical volumes (LVs) expose block addresses backed through the VG. Special thin-pool and cache-pool LVs represent pools, not ordinary block devices. [8] LV type determines allocation, striping, redundancy, snapshots and caching. Resizing an LV and resizing its filesystem are separate operations. [3]
vgcfgbackup stores VG configuration, not LV contents. It also excludes thin-pool mapping metadata. Restoring an older VG description with vgcfgrestore can mismatch the pool's current mappings and cause data loss; its force option does not establish consistency. [4] [6] [5]
A thin pool contains data and mapping-metadata components. Neither a configuration backup nor a spare metadata LV is an independent copy of the application data. [6]
For pvmove, abort is not necessarily a return to the original placement. An ordinary move keeps completed relocations, while a move started with --atomic retains source placement for the selected movement on abort. Background command return can precede relocation completion. [9]
Relations
- related
- Volume manager, Storage virtualization, Thin provisioning, Storage snapshot, Copy-on-write (storage), RAID, RAID 5, RAID 6, Striping (storage), JBOD, Mirroring (storage), Multipath I/O, Block storage, Thin pool, Thin-pool metadata, Snapshot exception store, Snapshot merge (LVM), Logical volume, Physical volume (LVM), Volume group (LVM), LVM pvmove
Advantages
- pvmove can relocate allocated extents between physical volumes. [3]
Limitations
- A linear or striped LV does not provide redundancy by itself. [3]
- Growing a block device does not prove that the filesystem has grown or that every lower storage layer has spare capacity. [3]
Citations
- LVM2 lvm(8): physical volumes, volume groups, logical volumes and commands
- LVM2 vgcfgbackup(8): volume-group configuration backup excludes LV contents
- LVM2 vgcfgrestore(8): thin-metadata mismatch and restore warning
- LVM2 lvmthin(7): thin-pool components, removal and recovery boundaries
- LVM2 lvcreate(8): thin-pool and cache-pool LV type restrictions
- LVM2 pvmove(8): extent selection, checkpoints, abort and background completion
Further reading
- Logical Volume Manager (Linux) — Wikipedia
- lvm(8) — LVM2 tools (Debian bookworm manpages)
- Hesela: Sparse files, preallocation and thin-pool capacity
Sources & caveats
- Current explanation follows primary LVM2 manuals; the older Wikipedia citation is retained for compatibility, not used for the recovery claims.
- This definition does not prescribe a restore procedure or report a recovery experiment.