Written by SirSiggi the 13 Apr 08 at 06:20.
Category: System.
Related project:
Nothing/Others.
Status: New
Rationale
Regular Filesystemchecks while booting are no bigger problem - most of the time. But if you are using a notebook on a presentation and the first thing you see on your beamer is a filesystem check, you tend to get a bit nervous.
There was a time when these checks could be aborted by pressing strg+c, but that is not possible anymore.
So why not just put those checks at shutdown or run them while the system is running and the user is working. Shouldn't create that much system load and wouldn't force the user to wait some minutes (big partition) and sweat the shit out of himself on stage...
It also would help on day to day situations where you just wanted to look something up in the internet and are forced to watch a progress bar.
I really don't see why anyone would want to use ext3 given its performance issues and the extremely long 'filesystemcheck'. I use a mixture of JFS and ReiserFS, never had any issues with either really although JFS feels slightly slower than Reiser but Reiser takes longer to mount (removing 'Filesystemcheck' from init.d improves boot performance no end and in all the years of using Ubuntu it hasn't caught a single problem for me)
In principle I agree, but my laptop wouldn't be connected to the projector while it's still booting...
I think you can also disable the checks with
tune2fs -c 0 /dev/sda1
and you could check where you are with
tune2fs -l /dev/sda1 | grep -i "mount count"
If you do that regularly, the check won't be such a surprise.
Another way is to stagger the file systems. My laptop has a 20G and 100G partition and the larger one is always checked one boot after the smaller one. Checking the 20G doesn't take long and when that happens I know that the 100G will be checked next time I boot the machine. So, basically I should know when that's coming.