thin-provisioning · shipping

Thin provisioning

Presenting logical storage capacity while allocating physical backing from a shared pool as writes require it.

Linux device-mapper thin pools separate logical mappings from underlying allocation. The no_discard_passdown feature removes mappings without forwarding discard to the data device; ignore_discard disables discard support. These modes are not equivalent. Reclamation at one layer does not establish erasure at a lower layer.

Logical volume size and filesystem free space do not establish pool headroom. LVM exposes Data% and Meta% separately; monitor both and verify that automatic extension has available volume-group space and time to respond. Linux v6.12 distinguishes metadata-space mode from a failed metadata transaction: the former can recover through metadata growth when needs_check is absent; the latter attempts rollback and sets needs_check, with failure of those steps forcing fail mode. [6] The displayed ro state alone does not identify which occurred. File preallocation is not evidence of an end-to-end reservation across this stack.

External-origin mode has another dependency: in-range unmapped reads use a separate, unchanged read-only origin, not pool data. This is an optional dm-thin configuration, not every thin volume. [7] [6]

Relations

related
Storage snapshot, Block storage, All-flash array, Discard, SCSI UNMAP, Sparse file, Hole punching, File preallocation, LVM, Thin pool, Thin-pool metadata, Usable capacity, Data-reduction ratio, Effective capacity, Thick provisioning

Limitations

  • A thin-pool mapping can be removed without a discard reaching the underlying device. [2]
  • Pool data and metadata are separate finite resources; sufficient logical capacity does not prevent exhaustion. [4, 2]
  • Metadata exhaustion must not be treated as merely waiting for an ordinary data-pool extension. [2]

Citations

  1. Linux 6.12: device-mapper thin provisioning, optional feature arguments (accessed 2026-10-11)
  2. LVM2: lvmthin(7), physical allocation, discards and pool exhaustion (accessed 2026-10-12)
  3. Linux v6.12: dm-thin.c, pool modes, timeout, failed metadata operations and resize (accessed 2026-10-17)
  4. Linux v6.12 dm-thin guide: External snapshots, read routing and descendant origin parameter. (accessed 2026-11-01)

Further reading

  1. Thin provisioning (accessed 2026-03-26)
  2. Hesela: Discard is not zeroing (accessed 2026-10-11)
  3. Sparse files, preallocation and thin-pool capacity (accessed 2026-10-13)

JSON: /data/terms/thin-provisioning.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Thin provisioning. Hesela. 2026-11-04. https://hesela.dev/terms/thin-provisioning/