Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs
On 18/08/2024 at 23:46, Pascal Hambourg wrote:
The /boot partition size is bigger than I expected in all LVM
cases, and I understand why. My previous calculations compensated the
LVM PV priority used by partman-auto-lvm but not the minimum size
(100MB) which is considerably smaller than the actual sum of lvmok
partition minimal sizes. According to my new calculations, it adds
~260MB to /boot.
This offset can be compensated by reducing /boot minimal size
(ironically it almost reverts to the previous value of 512MB) in recipes
where /boot exists only with LVM.
But it is not possible to do the same to the EFI partition or in recipes
where /boot exists in both LVM and non-LVM schemes. The only solution
I can think of is to replace the LVM PV fixed arbitrary minimal size
(and priority while we're at it) in partman-auto-lvm with the actual
values. But this may affect existing custom LVM recipes in unpredictable
ways. It is possible to apply the new behaviour only to built-in
recipes, but then custom recipes based on new built-in recipes may
produce unexpected results.
Another workaround could be to define the EFI partition twice in recipes:
- with $defaultignore and shifted minimum size,
- with $lvmignore + $cryptoignore and normal minimum size.
But it sounds like a hack again.
Reply to: