Once upon a time, XFS was available as an installation choice, and I used it for a couple of systems at the time.
It seems like the /boot partition is filling up, probably due to XFS journaling, and I rebooted a system with 0% available /boot space – it won’t come up again. Unfortunately, it’s a remote system.
I’m not really asking how to bring this system up again at this point. However it would be good to have checks for this scenario, or if XFS journaling is filling up /boot, run something to clear the journal before reboot/before running pakfire. Or even deprecate XFS, showing a warning in the UI if an XFS installation is detected.
Well, its a small drive, and I think /boot was 64 megs or so. Obviously, the check wasn’t working – and I have actually verified this on another system, also with a small /boot partition, also showing 0%. That machine also updated without error message and didn’t make the reboot but it is getting changed out tomorrow anyway, so…
I can upload the whole enchilada somewhere if you want but the relevant lines (from update-core-upgrade-137) seems to be these:
Extracting files...
boot/
boot/vmlinuz-4.14.150-ipfire
boot/System.map-4.14.150-ipfire
boot/initramfs-4.14.150-ipfire.img
boot/config-4.14.150-ipfire
tar: boot/config-4.14.150-ipfire: Wrote only 1024 of 10240 bytes
…
var/lib/suricata/classification.config
tar: Exiting with failure status due to previous errors
...Finished.
Stopping strongSwan IPsec...
…
Generating grub configuration file ...
Found background: /boot/grub/splash.png
Found linux image: /boot/vmlinuz-4.14.150-ipfire
Found initrd image: /boot/initramfs-4.14.150-ipfire.img
/usr/sbin/grub-mkconfig: line 262: echo: write error: No space left on device
There must be a bug in XFS handling or a filesystem corruption. The updater erase the old kernel which is 24MB before unpack the new one so it need nearly no additional disk space.
Is xfs not freeing the space of erased files properly?
This is what I wanted to see - or rather would have preferred not to.
I think there isn’t anything we can do about these systems now apart from trialing the mount options. However, they are up and running and we cannot change the partition size.
On new installations, the /boot partition should be large enough so that we won’t run into these problems any more.
How large is /boot nowadays, I see 110M on my reinstalled system?
At the very least, there should be a warning that one must reinstall the system (and pakfire shouldn’t run on XFS + small sized partition, I guess).
I guess you can still use gparted to enlarge the partition though?