On Sun, Mar 17, 2019 at 08:54:42AM -0600, Bdale Garbee wrote: > The complaint is not about a lack of space inside the filesystem, the > complaint is about a lack of unallocated space in the volume group. I > suspect a large number of users are now seeing this message from cron, > as I am, because they have a volume group where all blocks are > allocated. > > I think either the program itself or the cron invocation needs to be > updated to just not try and run the program when a volume group has no > unallocated space... I really don't want to see this error from cron > over and over!
Yeah, that's what I'm going to do. Will be uploading a new version shortly. For now, as a workaround, "systemctl disable e2scrub_all.timer ; systemctl stop e2scrub_all.timer" will stop the annoyance. (Or if you want to use this feature, just resize the file system so it's a bit smaller and also shrink the volume.) Apologies for the annoyance.... - Ted