FWIW, I run both ext3 and reiserfs on the same computer, and, after a crash, neither of them run fsck. My ext3 partition is mounted on /, so maybe it matters that it's mounted *before* it's fscked? The journal replay should mark it clean, so fsck should only run when it times out. You can also set the fsck number to "0" in your fstab, and it will never fsck, but then you will loose the periodic fscks. (I run 2.4.13-ac7-preempt-sse at the moment.)
Daniel
---
Recursion n.:
See Recursion.
-- Random Shack Data Processing Dictionary
On Wed, 7 Nov 2001 21:38:37 +0200
Ville Herva <vherva@niksula.hut.fi> wrote:
> On Wed, Nov 07, 2001 at 04:31:24PM +0000, you [James A Sutherland] claimed:
> >
> > Hm.. after a decidedly unclean shutdown, I decided to force an fsck here
> > and my ext3 partition DID have two inode errors on fsck... (Having said
> > that, the last entry in syslog was from the SCSI driver, and ext3's
> > journalling probably doesn't help much when the disk it's on goes AWOL...)
>
> A stupid question: does ext3 replay the journal before fsck? If not, the
> inode errors would be expected...
>
>
> -- v --
>
> v@iki.fi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Nov 07 2001 - 21:00:36 EST