hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

(bugfix) Bound snapshot storage metadata scans #100

New Issue
Closed
opened 2026-06-08 23:16:14 +02:00 by parkel · 0 comments
parkel commented 2026-06-08 23:16:14 +02:00
Owner
Copy Link

Snapshot storage metadata is currently collected by walking the snapshot data tree after backup completion. On very large backup targets this can be slow and memory-heavy because the scan tracks allocated inodes for hardlink-aware accounting. This can make worker finalization fail or OOM after rsync has already completed.

Acceptance criteria:

  • Snapshot storage metadata collection has a bounded scan mode used by backup workers.
  • Partial measurements clearly mark when they were limited/truncated.
  • Existing exact behavior remains available for small/test/direct usage where appropriate.
  • Backup completion should not OOM solely because a snapshot has too many files.
  • Tests cover scan limits and metadata flags.

Related feature/design follow-up: #98.

Snapshot storage metadata is currently collected by walking the snapshot data tree after backup completion. On very large backup targets this can be slow and memory-heavy because the scan tracks allocated inodes for hardlink-aware accounting. This can make worker finalization fail or OOM after rsync has already completed. Acceptance criteria: - Snapshot storage metadata collection has a bounded scan mode used by backup workers. - Partial measurements clearly mark when they were limited/truncated. - Existing exact behavior remains available for small/test/direct usage where appropriate. - Backup completion should not OOM solely because a snapshot has too many files. - Tests cover scan limits and metadata flags. Related feature/design follow-up: #98.
parkel added the area: observabilitybugfix labels 2026-06-08 23:16:14 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label area: observability bugfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#100
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?