>From: [email protected] > If you are mounting the file system read-only, feel free to change the > fsck pass number in /etc/fstab to be 0. That will cause e2fsck to be > skipped completely.
Wrong behavior. The desire here is not to disable checks due to being on read-only media, but the filesystem is much less likely to incur damage due to normally being read-only. The best example is /usr and sometimes /, where it is *very* important to catch errors, but not all that likely to incur them. > Note that mount count is randomized these days, to try to avoid > multiple file systems from being checked in a single boot. Which is why I wasn't writing about the mount count. I was writing about the check interval/check time. With systems that reboot less than once a month, the mount count will never be reached. Instead it will be the check interval and worse yet, with infrequent reboots, *all* of the check intervals will expire at once (even if they start spaced out, they will tend to merge together). > Also feel free to disable the precautionary checks if you don't want > to use it using tune2fs(8). If you are confident that your hardware > is perfect, and hard drive will never corrupt your metadata blocks, > the precautionary checks can easily be dsiabled. I'm not. I'm pointing out the behavior needs more refinement. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP F6B23DE0 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
