Assuming you're using a modern FS (e.g. xfs or ext4), you can probably get away with skipping it. You can always run it manually after an unclean shutdown as required, but I don't think it needs to be run regularly on a modern journaling FS. And if you use a next-gen FS like btrfs, it's not even an option - e.g. there is no (useful) fsck utility for btrfs, and one isn't all that necessary since the filesystem has built-in protections for consistency issues.
If you're still on ext2 or ext3, it's time to move to ext4. The latest Linux kernels even removed all of the ext2/3 code <https://lkml.org/lkml/2015/7/15/438> (although the ext4 code still provides backwards compatibility for ext2/3 where necessary). It's 2016 - using at least ext4 or xfs if not an unreasonable ask. We're even to the point where next-gen systems like btrfs or zfs are viable options (if still a bit greener). On Sat, Feb 6, 2016 at 12:14 PM, Cowboy <[email protected]> wrote: > On Saturday 06 February 2016 02:03:49 pm Rob Landry wrote: > > Does anyone know why I shouldn't disable these automatic filevsystem > > checks? > > yes ! If the file system has become damaged fir any reason, unlikely > as that may be with ext2 or ext3, there would be no recovering. > > It's grief when that mandatory boot fsck happens, I know, and one > of these days I'll make it optional. > ( today isn't the day ) > I'm not sure there's any good reason for it on ext3 anyway. > > -- > Cowboy > > http://cowboy.cwf1.com > > Any clod can have the facts, but having an opinion is an art. > -- Charles McCabe > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
