the fsck man page says
" -y For some filesystem-specific checkers, the -y option will cause
the fs-specific fsck to always attempt to fix any detected
filesystem corruption automatically. Sometimes an expert may be
able to do better driving the fsck manually. Note that not all
filesystem-specific checkers implement this option. In particu‐
lar fsck.minix(8) and fsck.cramfs(8) does not support the -y
option as of this writing."
that makes the benifit of manual checking seem pretty small. maybe the
-y option could be add by default.
Could a 'these files may have been damaged' list be given to the user at
next log in?
--
fsck not repairing corruption on boot
https://bugs.launchpad.net/bugs/209416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
