Add startup retention reclaim to recover from a full disk#88
Merged
Conversation
Ongoing retention removes a segment's manifest entry before destroying its backing data. When the process starts against an already-full disk that order cannot make progress: deleting the manifest row is a SQLite write that itself needs free space to journal, so it panics with "database or disk is full" before any space is reclaimed. Add Catalog::reclaim, a one-shot check run before the steady-state checkpoint/retention loops. When over the limit it removes the oldest segment data-first (destroy backing data, then remove the manifest entry), freeing space so the regular retention loop can take over. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01Jkk2NoeuqoKS8XsxZSu7gq
imp
force-pushed
the
fmurphy/startup-full-disk-recovery
branch
from
ca5b29a to
49dfdce
Compare
imp
approved these changes
Jun 30, 2026
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
3 participants
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.
Ongoing retention removes a segment's manifest entry before destroying its backing data. When the process starts against an already-full disk that order cannot make progress: deleting the manifest row is a SQLite write that itself needs free space to journal, so it panics with "database or disk is full" before any space is reclaimed.
Add Catalog::reclaim, a one-shot check run before the steady-state checkpoint/retention loops. When over the limit it removes the oldest segment data-first (destroy backing data, then remove the manifest entry), freeing space so the regular retention loop can take over.
Claude-Session: https://claude.ai/code/session_01Jkk2NoeuqoKS8XsxZSu7gq