2 ms·
If you have a large (multi TB) filesystem, sometimes those can take a long time to fsck. And if the fsck is just a scheduled one (after x reboots) instead of b
by justinclift 9y ago
If you have a large (multi TB) filesystem, sometimes those can take a long time to fsck.
And if the fsck is just a scheduled one (after x reboots) instead of being triggered due to filesystem weirdness, then getting the server back up and serving can be the higher priority.
That's just an example because you asked though. Wouldn't want that same fsck to be skipped if it was actually started due to filesystem weirdness being detected. :)