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.
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.