guest: avoid reserving unusable CAS blocks - #31
Open
zbarsky-openai wants to merge 1 commit into
Open
zbarsky-openai wants to merge 1 commit into
zbarsky-openai wants to merge 1 commit into
Conversation
The guest CAS is a dedicated ext4 filesystem, but mke2fs reserves 5% of its blocks for root by default. Build actions run under an unprivileged sandbox UID, so they fail with ENOSPC while gigabytes remain unused. A 56 GiB CAS image loses 2.8 GiB this way. Create new CAS images without reserved blocks and mount existing images with reserved space assigned to the configured sandbox UID. Existing cached action outputs remain intact.
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.
The guest CAS is a dedicated ext4 filesystem, but mke2fs reserves
5% of its blocks for root by default. Build actions run under an
unprivileged sandbox UID, so they fail with ENOSPC while gigabytes
remain unused. A 56 GiB CAS image loses 2.8 GiB this way.
Create new CAS images without reserved blocks and mount existing
images with reserved space assigned to the configured sandbox UID.
Existing cached action outputs remain intact.