RE: efivarfs_set_variable: writing to fd 8 failed
> -----Original Message-----
> From: Steve McIntyre <steve@einval.com>
> Sent: Thursday, January 9, 2020 2:42 PM
> To: junky@mail.sheugh.com
> Cc: debian-efi@lists.debian.org
> Subject: Re: efivarfs_set_variable: writing to fd 8 failed
>
>
> [EXTERNAL EMAIL]
>
> On Thu, Jan 09, 2020 at 06:33:14PM +0000, junky@mail.sheugh.com wrote:
> >On Wed, Jan 08, 2020 at 04:04:40PM +0000, Steve McIntyre wrote:
> >> [ Re-adding the cc to the debian-efi list - please respond there
> >> too... ]
> >>
> >> On Sat, Jan 04, 2020 at 10:55:51PM +0000, junky@mail.sheugh.com wrote:
> >> >> On Sat, Dec 28, 2019 at 03:39:32PM +0000, junky@mail.sheugh.com wrote:
> >> >> >Dear Maintainer,
> >> >> >
> >
> >> Sorry, I possibly wasn't clear enough. For UEFI, the NVRAM is normally
> >> an entirely separate set of storage (typically a flash chip) managed
> >> by the motherboard's firmware. It's nothing to do with your SSD or
> >> hard drive, it's more like an updated version of how BIOS settings
> >> used to be stored.
> >>
> >> One possible culprit here could be error logs stored in
> >> /sys/fs/pstore/ taking up lots of space. Could you check and see if
> >> you have any files there please?
> >
> >Best guess : 200 files of less than 2K each in /sys/fs/pstore
>
> Bah. :-( If you look at the filenames, you'll probably find that
> they're named something similar to the following:
>
> /sys/fs/pstore/dmesg-erst-6661505009219272707.enc.z
>
> (which is on one of my systems locally). The kernel can sometimes drop
> error logs there, but doesn't clean them up. If you remove the files
> yourself, then that should clear the space and fix your problem.
>
Given how small the pstore is, if the kernel has a tendency to directly drop files
here I think it makes perfect sense to have some process on the system
that regularly moves them out to somewhere else. Probably not only for
Debian but as a general statement.
Maybe something like systemd should prune on bootup and append to a previous
boot log for example.
Reply to: