[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How come fsck still kicks in and reports major errors with Ext3?



On Tue, Oct 29, 2002 at 05:10:05PM +0000, Stephen Tweedie wrote:
> 
> That's right --- after an unclean shutdown, fsck will run, but it will
> only perform a journal replay.  fsck on ext3 does *NOT* scan the full
> filesystem unless the forced fsck interval has elapsed or the
> filesystem has been marked as containing an error that needs fixing.

Just to further emphasize the point which Stephen made --- the reason
distributions run e2fsck even on ext3 volumes is because it's
important that fsck check to see whether or not the filesystem is
marked as containing an errors (it does this after replaying the
journal).  If kernel detected an inconsistency in the filesystem, it
really should be fixed in order to avoid potential data loss.

So Red Hat is really doing the right thing by forcing e2fsck to be run
on the filesystem.  As you'll note, it doesn't take very long if all
it needs to do is to replay the journal (and if you don't do it by
running e2fsck, the kernel will do it when you mount the filesystem,
so it doesn't save any time by removing the fsck).

					- Ted





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]