Do not count content already in the store when estimating a snapshot's size #170

Closed
opened 2026-10-26 01:52:10 -05:00 by ethan-hann · 1 comment
Owner

The snapshot space check sums the raw size of every new or changed file. A file whose content is already stored (switching back to a known version, a reverted file) adds nothing to the store, so a nearly full drive can be refused for a snapshot that would fit. Hashing is too slow for a pre-check; a cheaper signal may be the index stat match against known blobs, or treating files whose size and name match a stored entry as already stored.

The snapshot space check sums the raw size of every new or changed file. A file whose content is already stored (switching back to a known version, a reverted file) adds nothing to the store, so a nearly full drive can be refused for a snapshot that would fit. Hashing is too slow for a pre-check; a cheaper signal may be the index stat match against known blobs, or treating files whose size and name match a stored entry as already stored.
ethan-hann added this to the Later milestone 2026-10-26 01:52:10 -05:00
Author
Owner
Fixed in 0.9.19 (PR 252): https://git.tortal.tech/ethan-hann/SavePoint/releases/tag/v0.9.19
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ethan-hann/SavePoint#170
No description provided.