also sprach Phillip Susi <ps...@ubuntu.com> [2014-12-16 21:49 +0100]: > I think there is some expectation mismatch going on here. Aside from > the mount count check, e2fsck normally skips the check if the dirty > flag is not set. If the FS is currently mounted, then the dirty flag > is set, so trying this test at that time would always say there is > going to be a long fsck. As a result, the answer to the question > "will there be a long fsck on the next boot" depends on whether or not > the system will be shutdown cleanly or not, so you really can't ask > the question and get a meaningful result. The only thing you can get > a meaningful result from is "will the mount count limit be reached on > the next boot"?
… or will there have been 180 days since the last check. A bit of context: I am intending to analyse the answer to this question as part of the admin's call to /sbin/reboot, so we can assume a clean shutdown indeed. The chance of an unclean reboot between typing /sbin/reboot and the actual reboot should be about as high as the chance of /sbin/reboot being typed 3–5 seconds before those 180 days elapsed, and can in both cases be ignored. -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "the intellect is not a serious thing, and never has been. it is an instrument on which one plays, that is all." -- oscar wilde
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
