docs: Vault snapshots restored; record the permanent gap - #608
Merged
Merged
Conversation
A snapshot landed on the cold tier - vault-snap-20260923-151859.snap, 74271 bytes. The token's properties were checked rather than just its existence: orphan true, period 768h. A fresh non-orphan token would have produced an identical successful snapshot today and died again in 26 days. Records two near-misses in the verification. wc -c on the token file returns Permission denied as swares, which reads like a missing file when moving quickly; sudo head -c 4 discriminates hvs. from Erro, which is what tee writes when the create fails. And the first systemctl start never ran - swallowed by a paste - while systemctl is-active reported failed from the previous night's timer, so a latched failure is indistinguishable from a fresh one. Records the permanent hole: retention resumed with the job and -mtime +30 had not run since Sep 8, so about seven old snapshots aged out in one pass. The restore timeline is Aug 24 to Sep 8, a 15-day gap, then Sep 23. Vault's mid-September state cannot be reconstructed. Ticks when the gap ages out naturally after 2026-10-23. Heading deliberately says 'snapshot restored', not RESOLVED. Three of the four remaining items belong to other sections - token hygiene, alert delivery, journal retention - and calling the entry resolved would have made all four orphans, which is precisely how 7.y's twenty-five were manufactured.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A snapshot landed on the cold tier - vault-snap-20260923-151859.snap, 74271 bytes. The token's properties were checked rather than just its existence: orphan true, period 768h. A fresh non-orphan token would have produced an identical successful snapshot today and died again in 26 days.
Records two near-misses in the verification. wc -c on the token file returns Permission denied as swares, which reads like a missing file when moving quickly; sudo head -c 4 discriminates hvs. from Erro, which is what tee writes when the create fails. And the first systemctl start never ran - swallowed by a paste - while systemctl is-active reported failed from the previous night's timer, so a latched failure is indistinguishable from a fresh one.
Records the permanent hole: retention resumed with the job and -mtime +30 had not run since Sep 8, so about seven old snapshots aged out in one pass. The restore timeline is Aug 24 to Sep 8, a 15-day gap, then Sep 23. Vault's mid-September state cannot be reconstructed. Ticks when the gap ages out naturally after 2026-10-23.
Heading deliberately says 'snapshot restored', not RESOLVED. Three of the four remaining items belong to other sections - token hygiene, alert delivery, journal retention - and calling the entry resolved would have made all four orphans, which is precisely how 7.y's twenty-five were manufactured.