mount sticky disk with noinit_itable to stop repeated lazy-init writes - #123
Merged
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
adityamaru
approved these changes
Jul 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
2 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.
Summary
The builder sticky disk is formatted with
mkfs.ext4 -E lazy_itable_init=1, which defers inode-table zeroing to a background kernel thread (ext4lazyinit) that runs after mount. Sticky disks are copy-on-write clones of a committed snapshot: if the entity's snapshot was taken before lazy init finished (common for rarely-committing or depth-throttled builder disks), every subsequent clone replays the same multi-GB zeroing, and those Ceph writes are discarded with the clone — they never converge.Fix: mount with
-o noinit_itableto disable the zeroing thread. It is not needed for correctness — mkfs enables checksummed group descriptors that track unused inodes, and unallocated blocks on the thin-provisioned RBD device already read back as zeroes.Same fix as useblacksmith/stickydisk#68; this should also be applied to
release/v2after merge (mount code is identical there).Link to Devin session: https://app.devin.ai/sessions/1054a9452e8a49ccb891391e2327a612
Requested by: @piob-io
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled. (Staging)