You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Restore replica scheduling headroom for the next declared V1 claim #6282
The existing bounded V1 reservation repair handles only its original pair of claims. A later legitimate claim can exhaust a disk's logical replica budget and remain below its requested redundancy even when the physical free-space safeguards permit another copy. The V2 migration must hold until the source volumes have their required healthy copies.
Outcome
Restore the missing copy through the existing protected production workflow, with a narrowly reviewed allocation plan for the declared affected claim. Preserve the complete disk ledger, physical free-space floor, original data and all existing recovery gates.
Acceptance
Reproduce the refused current case and distinguish it from the historical repair.
Bind any reservation adjustment to complete current inventory, unchanged source and identities, two intact peer copies, the exact missing allocation, and the existing free-space margin.
Keep unrelated or ambiguous degraded volumes, competing maintenance, changed identities and uncertain writes closed.
Verify the original affected volume regains all requested healthy replicas before accepting recovery or continuing migration.
#5969 - fix(storage): restore capacity for missing V1 replicas [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
The original affected encrypted source volume now has its full requested redundancy: the backend is healthy, three replicas run on distinct workers, and the engine reports all three as RW. Fresh read-only native inventories confirm the same original volume identity. Normal scheduling recovered the missing copy after the first retained recovery copy was removed through #6041.
No reservation repair was needed or dispatched. The unused draft #6289 is closed. Closing this outcome as recovered; #5582 remains open for the full V2 migration and the remaining cleanup. Detailed native receipts remain private.
Activity
coderabbitai commentedon Nov 14, 2026
🔗 Related PRs
#5969 - fix(storage): restore capacity for missing V1 replicas [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #6282 nonce=da337446f13cc7d64fcbb6a9a33a5ee0
chore: agent-claim #6282 nonce=2e20cd5a6fe947ac8e6a0b57728937c7
devantler commentedon Nov 15, 2026
The original affected encrypted source volume now has its full requested redundancy: the backend is healthy, three replicas run on distinct workers, and the engine reports all three as
RW. Fresh read-only native inventories confirm the same original volume identity. Normal scheduling recovered the missing copy after the first retained recovery copy was removed through #6041.No reservation repair was needed or dispatched. The unused draft #6289 is closed. Closing this outcome as recovered; #5582 remains open for the full V2 migration and the remaining cleanup. Detailed native receipts remain private.