Thanks for the link; for some reason it doesn't work for me at the moment. I'll try it again later.
Should a system need to shut down right now because a UPS has indicated that its battery is nearly exhausted, running a lengthy fsck could be a Bad Thing(tm). A common enterprise solution is to disable all of the automatic fs checks ("tune2fs -c 0 -i 0") and do those checks during scheduled maintenance time.
My intention is to give myself an alternative to the ordinary shutdown button, and to do the fs checks while I'm cleaning my teeth and getting ready for bed. Not quite an enterprise solution, I agree.
One thing I haven't seen clearly explained is what should govern the choice of max mount count and check interval. (They seem often to be 26 mounts and 180 days, which smacks of the 1970s: start the System 360 on Monday morning, do a tape backup and shutdown on Friday evening, and check fs every 6 months.)
So what corrupts file systems? Is it mounting/unmounting, reading files, writing to them, fragmentation, mechanical stuff like misaligned heads and misbehaving drive motors, magnetic degradation through heat, vibration, or passage of time, cosmic radiation, or some combination of all of the above and other things I haven't thought of?
And in 2012 with fairly modern hardware and a journalled file system like ext3 or ext4 what are reasonable choices for max mount count and check interval?