Looking at the logs, I'm now convinced the '-f' argument is added to
fsck. It looks like the real issue is that the user isn't notified that
an fsck is happening and the user isn't given the option to cancel the
fsck (regression from Jaunty). I'll mark this bug as invalid and open a
new bug (if one doesn't already exist).
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
/forcefsck doesn't add '-f' argument to fsck (for ext4, ext3, ext2)
https://bugs.launchpad.net/bugs/435707
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
