Skip to content

docs: clarify snapshot dedup behavior across scan modes - #349

Open
Finomosec wants to merge 1 commit into
Zygo:masterfrom
Finomosec:docs/clarify-snapshot-scan-modes
Open

docs: clarify snapshot dedup behavior across scan modes#349
Finomosec wants to merge 1 commit into
Zygo:masterfrom
Finomosec:docs/clarify-snapshot-scan-modes

Conversation

@Finomosec

Copy link
Copy Markdown

Summary

  • Rewrites the Snapshots section in gotchas.md to distinguish between scan modes
  • Documents that extent scan mode (v0.11+, default) uses LOGICAL_INO to discover and dedupe all snapshot references in a single pass, avoiding the per-snapshot scanning cost of older subvol scan modes
  • Adds a note about v0.12 improvements (back-to-back dedupes, ~1/10th overhead per snapshot on NVMe)
  • Clarifies that metadata growth is intrinsic to btrfs and applies regardless of scan mode
  • Adds a third case study for extent scan mode behavior
  • Annotates the existing "non-empty filesystem" case study as applying to subvol scan mode

Prompted by this comment suggesting a docs update to clarify the snapshot limitation.

🤖 Generated with Claude Code

The Snapshots section in gotchas.md described snapshot dedup behavior
that only applied to older subvol scan modes. Since v0.11, extent scan
mode (the default) uses LOGICAL_INO to find all references to an extent
including snapshot copies, deduping them together in one pass.

Update the documentation to distinguish between scan modes, add a note
about upcoming v0.12 improvements, and add a case study for extent scan
mode behavior.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant