Description of problem: When installing kernels, it do not detect that /boot get full. To the user, it looks like the process ends successfully. In the log you find i.e: [morgan@svarten ~]$ journalctl -b | grep 'No space left' jul 28 22:26:36 svarten.tribun plasmashell[240543]: cp: error writing '/boot/initrd-6.12.39-desktop-1.stable.mga9.img': No space left on device jul 28 22:27:30 svarten.tribun plasmashell[251350]: cp: error writing '/boot/initrd-6.6.100-desktop-1.mga9.img': No space left on device How reproducible: It have been like this forever i think, i got used to it... Still it is serious.
Did you install remove old kernels ? Is just a workaround but is something
Regardless of anything else, any install errors should be reported to user. rok only uninstalls kernels when it is run - manually or by cron. Example: On my workstation I did not intend to do much kernel testing, but now I test all three standard flavours plus backport. Updating brings in three or four new kernels. My half gig /boot is about half full with four kernels, a full standard update of all and it fail. So the standard setting of rok do not help. That said having a separate /boot is not default install either. Bottom line - report any fail to the user.
A simple test like LC_ALL=C df /boot --output=avail|grep -v Avail and compare the value with the initrd image will help LC_ALL=C before df is a mandatory to not complicate the command with the possible translations LC_ALL=C df /boot --output=avail|grep -v Avail 25G df /boot --output=avail|grep -v Disp 25G In my system
Yes the tool should perform that test On my system, separate /boot partition: $ LC_ALL=C df /boot --output=avail Avail 216M