Control: clone -1 -2 Control: reassign -2 src:linux Control: retitle -2 linux-*: Provide information about /boot space usage Control: seveirty -2 wishlist On Wed, Oct 16, 2024 at 07:49:05AM GMT, Paul Gevers wrote: > Package: apt > Version: 2.9.8 > Severity: normal > > Hi, > > I think I just spotted a new feature of apt (thanks for the continuous > improvements): reporting and protection of /boot. However, I think it was > far off and hence prevented me from upgrading without looking into it. > > Story is that some time ago, my /boot was too small (it came with Debian's > default) for upgrades of the kernel, and I was advised on IRC to configure > something regarding modules (IIRC something like: as-needed) which > drastically reduced the used size in /boot to the extend I haven't had to > worry about it anymore. Today it was different. > > Starting point: > > paul@mulciber ~ $ sudo apt full-upgrade --update > ... > Installing dependencies: > linux-doc-6.11 linux-image-6.11.2-amd64 I would assume that this is the culprit, the calculation is size of (linux-image-6.11.2-amd64) + ( largest initrd + largest map ) * 1.1 It seems Debian kernels include modules in their image package, causing the modules to be counted. An Ubuntu kernel image (which I tested this against) meanwhile is true to the name and only contains the kernel image (the modules are in linux-modules-$(uname -r)). What are our ways out here? * Split modules out of linux-image into linux-modules * Add a new Boot-Size: field indicating the size of files in /boot * Change the estimate to use the largest kernel size. This is much more unreliable. We also need to have a look at packages triggering initrd generation: Technically you need space for one additional initrd in /boot as the new file is being written before the old one is deleted. :( -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Attachment:
signature.asc
Description: PGP signature