Often times in the heat of a critical server restart the system decides to FSCK a very large filesystem. If I let it take its natural course it could be a day before its back (for 12TB file systems using ext3). So to stop it from fscking follow this procedure.
1) Restart system
2) When it begins FSCKing, it will start running a percentage counter. Crtl-C from this. It will dump you to Repair Filesystem mode
4) Once in repair after entering the root password you will need to edit fstab to comment out the partition. This fails as it is unable to edit the file as its Read-Only.
3) Run the command “mount -o remount /” or to be absolutely sure “mount -n -o remount,rw /”
4) Comment out the partition in /etc/fstab and restart the box.
5) Once the box has recovered uncomment the partition and mount it.
6) Schedule downtime for the box for fscking.
This doesn’t take into consideration the negative affects of running an ext3 filesystem without fsck for that long a period and cheating to get around it. But there are times when things just have to be fixed ASAP, this comes in handy.