I'm not sure I under stand what you're saying here? It sounds like one filesystem hadn't been checked after 29 mounts, said it would be checked on the next reboot, and oin the next reboot it was checked.
Could it be that you had another filesystem on your filesystem that was ready to be checked, and it was checked on this boot cycle? How many filesystems do you have on your system? The number of mounts before a check are intentionally randomized to avoid (or at least make much, much less likely) that all of the filesystems on the system needing to be checked all at once. But it could be that one filesystem would be checked after the next boot, but the second filesystem was due to be checked at the current boot. That might explain what you saw. Othetrwise, I'm not sure what you are reporting/complaining about. Regards, -- FSCK run twice https://bugs.launchpad.net/bugs/66316 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
