>> >> Probably, but why would you want to? it fixes any errors, and makes the >>file >> >> system relatively clean again so that things function well - and things >>don't >> >> get lost. >> >> If you skip it, you risk data corruption on disk. >> > >> > That misses the point. I have rebooted sometimes just for a quick >> > change, possibly to try a different kernel, and intending to reboot >> > several times. Then whoops! it starts a long fsck scan, not to repair >> > damage, but just because some counter went to zero. What a waste. >> > >> > It's like insisting on an oil change exactly every 3000 miles. No, >> > sorry, I will wait until it is convenient for *me*, not the odometer. >> > >> > So his question is, once the fsck has started, can he ^C to bomb it >> > off, or do anything else to skip what has started? >> >> Exactly. I couldn't get it to stop with ^C or i or I. >> > > No. You can't. Nor do you want to at that point. > Once it has started it really should run until completion otherwise you really > risk data corruption. > If you want to stop it, you have to prevent it from starting in the first > place.
Yeah, that can really be a drag. Last night my Gentoo HTPC checked the 2TB drive for 2 hours when I rebooted after a movie we were watching froze. - Grant
