Inadequate /boot space requirement estimation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Yesterday I experienced a "no space available" condition on /boot during do-release-upgrade of a server from trusty to xenial.
Excerpt from the apport log (it contains somewhat sensitive information so It'll need cleaning to be disclosed):
Sætter linux-image-
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
update-initramfs: Generating /boot/initrd.
cat: skrivefejl: Ikke mere plads på enheden
update-initramfs: failed for /boot/initrd.
run-parts: /etc/kernel/
dpkg: fejl under behandling af pakken linux-image-
underproces installerede post-installati
Translations from Danish:
"Sætter <package> op ..." = "Setting up <package>"
"skrivefejl: Ikke mere plads på enheden" = "write error: No space available on device".
Before do-release-upgrade was satisfied to commence with the upgrade I had to free space on /boot manually. I did this by explicitly removing old kernels using dpkg -r, because apt-get autoremove wanted to upgrade to a new 3.13.0-163 kernel (system was running 126) before removing old ones, which it couldn't. Afterwards I assured that only files related to the current 126 and the previous 125 kernel was present in /boot, by removing all other image packages and manually removing some initrd (maybe others also) files relating to those still present in /boot.
Even though the release upgrade was now satisfied to continue it still failed during the initrd generation for the kernels because of too little space available on /boot.
Subsequent inspection of /boot showed the new vmlinuz-4.4.0-140 kernel was installed but the initrd was obviously missing. Still there were now files related to older 3.13.0-
I am a bit puzzled by the older kernels still having files generated in /boot. The system had linux-headers packages installed for some of those but I guess this shouldn't be enough to warrant space being used in /boot? At least after a normal upgrade cycle they are still not back (header packages still being installed) but this could in theory be handled different from the release-upgrade.
I can see from https:/
Log started: 2017-06-29 13:52:42
Gør klar til at udpakke .../python3-
Udpakker python3-distupgrade (1:0.220.9) over (1:0.220.8) ...