regular fsck runs are too disturbing
erik.andren at gmail.com
Sun Oct 21 20:13:24 UTC 2007
I'm going to add an anecdote to this thread why running fsck (at least in
textmode) at startup is bad.
Some good friends of mine use ubuntu on their HTPC. The connected HDTV can't
display the text mode under which the fsck runs, this results in a blue
screen during the whole operation. As these folks aren't any computer
whizzes they belive the computer has hanged itself as no plausible
explanation is given from the computer. Efter a brief explanation from me
this, of course, is no problem, but I'm sure these people aren't the only
one with a similar experience.
2007/10/17, Phillip Susi <psusi at cfl.rr.com>:
> Onno Benschop wrote:
> > I am subscribed to the list, there is no need to send this to me
> Fair enough. I will remove you for now, but if you wish to not get such
> replies regularly, you should set your Reply-To: header to point to the
> mailing list.
> > I have personal experience where "a modern journalling file system"
> > (ext3) does *not* maintain integrity. I have now had three cases where
> > the journal corrupted for no particular reason, causing the kernel to
> > remount my drive read-only. A read-only and non-destructive read-write
> > test failed to uncover any problems.
> > My point was, and it still stands, "theoretically a file-system
> > maintains its integrity, in practice it cannot".
> > fsck is the tool that catches the difference between theory and
> It sounds like in your case it was the running kernel that noticed the
> problem ( which in all likelihood was simply an IO error that happened
> while the kernel tried to update the journal ), not the auto fsck at 30
> mounts. In any case, such errors occur only for the VAST minority of
> users, so why should everyone be penalized?
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ubuntu-devel-discuss