volume-manager · shipping

Volume manager

A volume manager maps underlying block-storage resources into logical volumes and manages their allocation and layout.

Related Observatory article: Read on hesela.com

Logical volumes separate the block devices presented to applications from the devices supplying their capacity. In Linux LVM, physical volumes form a volume group and device-mapper implements the logical-volume mappings. Linux dm-linear can map ranges within backing devices; a volume need not aggregate whole disks. [4] [2]

Features depend on the selected volume type. Aggregation does not itself imply redundancy, snapshots or thin provisioning. A linear volume and a mirrored volume have different failure behavior even though both are logical volumes. [2] [3]

Inspect the storage layers behind a visible volume rather than treating its name as a physical placement guarantee. LVM can use hidden sub-volumes between the visible device and physical storage. [3]

Volume management does not replace filesystem resize requirements. Reducing an LV while its filesystem still uses the removed region can destroy data; a supported filesystem reduction must finish before the containing LV is reduced. [5]

Relations

related
RAID, Thin provisioning, LVM, Storage virtualization, Block storage, Storage snapshot, Snapshot exception store, Logical volume, Physical volume (LVM), Volume group (LVM)

Advantages

  • Applications can use a virtual block device instead of depending directly on the underlying physical-device layout. [2]

Citations

  1. LVM2 lvm(8): virtual block devices and logical-volume types (accessed 2026-10-22)
  2. LVM2 lvconvert(8): --mergesnapshot and activation (accessed 2026-10-22)
  3. Linux kernel: dm-linear block-range mappings (accessed 2026-10-24)
  4. LVM2 lvreduce(8): filesystem ordering and data-loss warning (accessed 2026-10-24)

Further reading

  1. Volume manager (accessed 2026-03-26)
Sources & caveats
  • The general concept is illustrated with Linux LVM2; other volume managers can use different allocation and metadata designs.
  • The original c1 citation and stable identifier are retained. The expanded explanation uses the primary LVM2 manuals.

JSON: /data/terms/volume-manager.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Volume manager. Hesela. 2026-10-24. https://hesela.dev/terms/volume-manager/