New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

200MB default boot partition size too small #3224

Open
qubesuser opened this Issue Oct 27, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@qubesuser

Qubes OS version:

R4.0-rc2

Steps to reproduce the behavior:

  1. Install Qubes using default settings (tested with EFI), or look at the default partition layout in custom partitioning

Expected behavior:

Boot partition is at least 500MB, preferably 1GB large.

Actual behavior:

Boot partition is 200MB

General notes:

200MB is enough for the current use case, but potentially impedes future features as well as tinkering by power users. Since it's very difficult to change, a larger size seems warranted. Other distributions also seem to have adopted or be moving towards 500MB+ sizes.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 30, 2017

Member

On default non-EFI installation, /boot is about 1GB. On EFI, /boot/efi should be 500MB, and no separate /boot should be created. Apparently the latter doesn't work. 200MB is default value in Fedora, so that function either is buggy, or not called at all in the current anaconda.

Member

marmarek commented Oct 30, 2017

On default non-EFI installation, /boot is about 1GB. On EFI, /boot/efi should be 500MB, and no separate /boot should be created. Apparently the latter doesn't work. 200MB is default value in Fedora, so that function either is buggy, or not called at all in the current anaconda.

@qubesuser

This comment has been minimized.

Show comment
Hide comment
@qubesuser

qubesuser Oct 30, 2017

The 200MB is what the automatic partition creation button after choosing custom partitioning offered on my system.

Maybe that uses a different codepath? (it also defaults to LVM instead of LVM Thin Provisioning, so it seems it could be)

Also not quite sure about the logic in having different sizes between /boot and /boot/efi since the biggest space usage is Xen and the Linux kernels and initramfses, which are of course present in both cases.

The 200MB is what the automatic partition creation button after choosing custom partitioning offered on my system.

Maybe that uses a different codepath? (it also defaults to LVM instead of LVM Thin Provisioning, so it seems it could be)

Also not quite sure about the logic in having different sizes between /boot and /boot/efi since the biggest space usage is Xen and the Linux kernels and initramfses, which are of course present in both cases.

@andrewdavidwong andrewdavidwong added bug and removed task labels Oct 31, 2017

@evadogstar

This comment has been minimized.

Show comment
Hide comment
@evadogstar

evadogstar Dec 1, 2017

Please, remember, that some users still at 128Gb SSDs. :)

Please, remember, that some users still at 128Gb SSDs. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment