| |||||||||||||
ext3 metaclusteringext3 metaclusteringPosted Jan 17, 2008 13:42 UTC (Thu) by glm (subscriber, #45719)In reply to: ext3 metaclustering by tialaramex Parent article: ext3 metaclustering
There is another (less radical) workaround against an unwanted "maximal mount count" boot-time check: simply interrupt the check with Ctrl+C. This will defer the check until the next boot-time, hopefully on a less time critical occasion.
(Log in to post comments)
ext3 metaclustering Posted Jan 17, 2008 15:20 UTC (Thu) by sbergman27 (guest, #10767) [Link] On all the distros I have tried, ctrl-c doesn't stop it. Nothing stops it. Not even if you are in a situation where a 30 minute forced fsck is *really* embarrassing. And it is "opt out". So one must remember to turn it off with tune2fs or expect it to kick in as a surprise when one can least afford it.
ext3 metaclustering Posted Jan 17, 2008 16:04 UTC (Thu) by nix (subscriber, #2304) [Link] That's because signals aren't delivered from the initial console by default, and the program which fixes that (getty) doesn't run until a long time after fsck runs.
ext3 metaclustering Posted Jan 17, 2008 17:39 UTC (Thu) by bronson (subscriber, #4806) [Link] So, how does one stop it? I suppose the right time to run the automatic fsck is when the volume is being unmounted at shutdown. I don't mind at all if the computer wants to chug along happily for 20 minutes and then power itself off. I sure as heck mind if it happens at startup and prevents me from using the computer for 1/2 hour in the morning! Any thoughts? Should I file an Ubuntu feature request?
ext3 metaclustering Posted Jan 17, 2008 20:29 UTC (Thu) by jzbiciak (✭ supporter ✭, #5246) [Link] Hmmm... does putting an "stty sane" early in the boot scripts make it work?
ext3 metaclustering Posted Jan 22, 2008 0:09 UTC (Tue) by fergal (subscriber, #602) [Link] This was just recently discusses on ubuntu-devel-discuss, the thread should be in the archives.
ext3 metaclustering Posted Jan 18, 2008 18:16 UTC (Fri) by ranmachan (subscriber, #21283) [Link] On Debian, the filesystem check can be stopped with Ctrl+C, at least for filesystems other than /. I'm not sure about /, since it _may_ be different and my / is usually small enough to just wait for fsck to finish. /home can be quite annoyingly long though and gets the Ctrl+C treatment sometimes.
|
|||||||||||||