Repository navigation
fix(write): report a stuck bitmap lock as EIO, not ENOSPC - #104
Merged
Merged
Conversation
Block allocation in write and fallocate mapped every bitmap or extent-tree allocation error to ENOSPC, including a lock wait that gave up and a bitmap sector that could not be read. Only an empty bitmap or full backing storage is ENOSPC now; everything else is EIO. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Follow-up to #66, which fixed only inode claims. Block allocation in write and fallocate still reported every bitmap or extent-tree allocation failure as ENOSPC, including a bitmap lock wait that gave up after 30s. On main,
TestAllocationReportsStuckBitmapLockAsEIOgets "no space left on device" from both a write and a fallocate while another node holds the bitmap lock. ENOSPC now means only an empty bitmap or a backing device that is itself full.Create, mkdir and copy-on-write already returned EIO for every allocation failure, so they never claimed a full device. When the device really is full, they still say EIO, not ENOSPC; that is not changed here.
🤖 Generated with Claude Code