Huh... do you really think, that the change not to show the message did solve that bug?
There is some process not reacting on int/term signals which prevents clean unmount of file system and thus forcing fsck to be run on the next system start.
Huh... do you really think, that the change not to show the message did solve that bug?
There is some process not reacting on int/term signals which prevents clean unmount of file system and thus forcing fsck to be run on the next system start.