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!

Bdale

Attachment: signature.asc
Description: PGP signature

Reply via email to