disk_layout: Keep Azure image size at 30 GB #3460
Merged
Conversation
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
The increased /boot and /usr partitions meant that we grew all images types. The raw image had the root partition decreased a bit but the VM images not, and AWS and Akamai images even got aligned to also have the larger VM rootfs instead of the raw rootfs. All image types are way smaller than Azure with its 30 GB size and thus the size had to be increased. For Azure, however, we already have enough free space and it is good to avoid increasing the image size because this requires action for those cases where users had assumed that the image fits into a hardcoded 30 GB disk. Reduce the root partition by the amount of blocks that is the difference between the old and current full disk image size for Azure. Signed-off-by: Kai Lueke <[email protected]>
chewi
approved these changes
Nov 3, 2025
pothos
added a commit
that referenced
this pull request
Nov 4, 2025
disk_layout: Keep Azure image size at 30 GB
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.
The increased /boot and /usr partitions meant that we grew all images types. The raw image had the root partition decreased a bit but the VM images not, and AWS and Akamai images even got aligned to also have the larger VM rootfs instead of the raw rootfs. All image types are way smaller than Azure with its 30 GB size and thus the size had to be increased. For Azure, however, we already have enough free space and it is good to avoid increasing the image size because this requires action for those cases where users had assumed that the image fits into a hardcoded 30 GB disk.
Reduce the root partition by the amount of blocks that is the difference between the old and current full disk image size for Azure.
How to use
Backport to the Alpha branch
Testing done
The new image size with this PR is:
The Azure image size with Beta (before the increase) was:
The Azure image size with Alpha (after the increase) was:
Jenkins ran to provide bincache images for further testing.
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.