Package: e2fsprogs Version: 1.41.3-1 Subject tells the story. Why are mere /precautionary/ filesystem checks allowed to slow a system booting so much? ie the ones triggered by either the mount count or check time exceeding their limits.
I would suggest limiting it to doing a precautionary check on *one* filesystem (or perhaps one filesysterm per drive) when booting. Also if a filesystem gets checked due to other issues, that should inhibit the precautionary check. This is particularly excessive for filesystems that only get mounted read-only. Read-only filesystems additionally do not need to halt the boot process when getting precautionary checks, since they can be checked in the background even while the kernel has them mounted. This is particularly troublesome for servers, since they don't get restarted very often, they're far more likely to trigger the check time, rather than mount count. This is problematic, since this is more than likely to trigger for *all* filesystems at the same time. -- (\___(\___(\______ --=> 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]
