mountall sets the second fsck to the idle IO priority until the first
fsck is finished, which prevents disk thrashing. The differences between
non-zero passno values are ignored intentionally.
You can verify that by adding “--debug >/dev/mountall.log 2>&1” to the
“exec mountall...” line in /etc/init/mountall.conf and rebooting with
forcefsck. The log should say something like “/home/joshua/imagefiles:
priority low” until the fsck for /home is done.
There’s a bug in mountall only if both fsck instances are run
simultaneously with the normal IO priority. If that is the case, please
attach /dev/mountall.log and change the bug status back to new. Thanks.
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
mountall ignores the pass parameter of /etc/fstab when scheduling fsck
https://bugs.launchpad.net/bugs/599624
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
