snapshot · shipping

Storage snapshot

A storage snapshot is a point-in-time representation of a filesystem or volume, whose implementation may share blocks with its source.

Related Observatory article: Read on hesela.com

OpenZFS snapshots are read-only views that initially share data with the active dataset. A snapshot held only in the source pool remains dependent on that pool; this is a failure-boundary inference, not a claim that snapshots cannot be used for backup. Recursive OpenZFS snapshot creation coordinates descendant datasets, not arbitrary independent pools. Application buffers and multi-volume consistency require separate consideration. Btrfs snapshots differ: nested subvolume contents are not captured by a parent snapshot. [8]

ZFS retention: dataset clones keep an origin dependency, while named snapshot holds are releasable deletion guards. Neither operation creates an independent recovery copy; inspect deferred-deletion state before releasing a hold. [10] [11]

ZFS space accounting: a snapshot's used counts exclusive space; usedbysnapshots is not the sum across snapshots. Deletion can raise a survivor's used. Pool freeing tracks asynchronous reclamation, not dataset write headroom. [12] [13]

Observation limits: zpool wait -t free observes pool freeing activity, not whether a selected snapshot was deleted. It can return with no activity, and pool export or destruction can end the wait. fsync and O_SYNC do not necessarily refresh space counters immediately. [14] [12]

Relations

related
Copy-on-write (storage), Thin provisioning, Air-gapped backup, Backup, Application-consistent snapshot, Crash consistency, Recovery point objective, Recovery time objective, Distributed snapshot, Backup verification, Restore test, Btrfs read-only subvolume, Filesystem freeze, Application quiescing, LVM, ZFS bookmark, ZFS receive resume token, ZFS raw send, Snapshot exception store, Snapshot merge (LVM), ZFS dataset clone, ZFS clone promotion, ZFS snapshot hold, ZFS deferred snapshot destruction, ZFS pool checkpoint, NOVA-Fortis, ViewBox, Spyglass

Advantages

  • Can retain an earlier view without immediately copying every data block. [3]
  • Can provide the source for a full or incremental send stream. [5]

Limitations

  • Periodic snapshots can miss short-lived files and intermediate changes between capture points; retaining snapshots longer does not recreate those missing states. [1]
  • Space usage can grow as the active dataset diverges from retained snapshots. [3]
  • For a running PostgreSQL server, filesystem snapshot backups require the complete cluster and WAL, captured simultaneously across the relevant filesystems. A documented alternative is to stop the server throughout capture. [6]
  • A classic LVM COW snapshot becomes invalid when its allocated change space fills; extending it must happen before exhaustion. [9]

Citations

  1. Strunk et al.: Self-Securing Storage: Protecting Data in Compromised Systems, OSDI 2000, section 6 (accessed 2026-10-15)
  2. OpenZFS v2.3: zfsconcepts(7), snapshots and storage pools (accessed 2026-10-13)
  3. OpenZFS v2.3: zfs-send(8), full and incremental streams (accessed 2026-10-13)
  4. PostgreSQL 18: File System Level Backup, section 25.2 (accessed 2026-10-13)
  5. Btrfs documentation: subvolume flags and non-recursive snapshots (accessed 2026-10-15)
  6. Red Hat Enterprise Linux 8: thick snapshot capacity, sections 67.4.2.2 and 67.8.1 (accessed 2026-10-22)
  7. OpenZFS v2.3: zfs-hold(8), named holds and release (accessed 2026-10-22)
  8. OpenZFS v2.3: zfs-destroy(8), dependent and deferred destruction (accessed 2026-10-22)
  9. OpenZFS v2.3: zfsprops(7), used and usedbysnapshots (accessed 2026-10-22)
  10. OpenZFS v2.3: zpoolprops(7), freeing and free (accessed 2026-10-22)
  11. OpenZFS v2.3: zpool-wait(8), activity cessation and free (accessed 2026-10-23)

Further reading

  1. Storage snapshot (accessed 2026-03-26)
  2. OpenZFS v2.3: zfs-snapshot(8), atomic and recursive snapshots (accessed 2026-10-13)
  3. Hesela: Snapshots and backups: which failures can you recover from? (accessed 2026-10-13)

JSON: /data/terms/snapshot.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Storage snapshot. Hesela. 2026-11-21. https://hesela.dev/terms/snapshot/