On Wednesday 07 November 2001 7:38 pm, Ville Herva 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...
Yes, it does: this was AFTER the journal replay. And yes, it was ext3 not
ext2 mounting it (well, either that or ext2 has learned to do journal
replays...). So, AFTER a journal replay, there were still two damaged inodes
- which sounds like Anton's problem. Maybe ext3 just hates Cambridge? :-)
James.
-
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