Sorry. I ran into this again, and thought: User sees a message at boot which of course flies by and is not saved in journalctl, something like ... has been mounted 20 times, check forced, ... could be ... IGNORED.
# strings /sbin/e2fsck |egrep 'could be|IGN' IGNORED @i %i @x tree could be more shallow (%b; could be <= %c) @i %i @x tree (at level %b) could be shorter. @i %i @x tree (at level %b) could be narrower. He thinks, "Hey, I've got to give this machine back to the client, and I promised him 'no problems'. I can't even find a way to fix it:" # man e2fsck |egrep -c 'could be|IGN' 0 "Nor is there any way to make cleaning up such stuff the default!" Anyway, the warning/info message should say 'use e2fsck -f -D? ... to fix'. (Or now checking the previous discussion: NO WAY TO FIX? Then how can one hand the machine back to the client in 'perfect condition'. If the client sees 'even one message', he will blame our company, etc. "And no, 2&>/dev/null will get our company even more embarrassment." Version: 1.43.3-1
