Bug#853237: ENOSPC errors should be more helpful
I've seen a growing number of people reporting efibootmgr failing with
ENOSPC when trying to add new boot entries, e.g. on grub-efi
upgrades. It's a worrying trend, and users are ending up with
unbootable systems (hence the severity).
#852513 is a great example. Norbert has done an excellent job of
investigating the problem (thankfully) and in his case this seems to
be a problem with the pstore filling up. Maybe this is the cause of a
number of these problems (e.g. #756253).
With ENOSPC error, at the very least, we should:
* warn users that their system may fail to boot
* give some ideas on what might be the cause
* suggest ways to investigate and/or fix the problem
We could even check for files in /sys/fs/pstore and complain if
they're taking up too much space, maybe?
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages efibootmgr depends on:
ii libc6 2.19-18+deb8u7
ii libefivar0 0.15-3
ii libpci3 1:3.2.1-3
ii zlib1g 1:1.2.8.dfsg-2+b1
efibootmgr recommends no packages.
efibootmgr suggests no packages.
-- no debconf information