On Wed, Nov 06, 2002 at 02:05:21PM +0100, Jens Axboe wrote:
> On Wed, Nov 06 2002, Stephen C. Tweedie wrote:
> >
> > error is just ext3's normal reaction to a fatal error detected in the
> > filesystem, so that in itself isn't a worry. The cause of the problem
> > it spotted is the worry; is this reproducible?
>
> I can try. The kernel run had my rbtree deadline patches, however
> they've been well tested and are likely not the cause of the problem. It
> cannot be 100% ruled out though, I'm testing for this very thing right
> now. I will let you know what happens.
I think I can rule that out, I've got much the same[1] from a vanilla
2.5.46, and the filesystem's recent history has been plain 2.5.XXs as
well.
Ewan
EXT3-fs error (device ide0(3,5)): ext3_new_inode: Free inodes count
corrupted in group 18
Aborting journal on device ide0(3,5).
ext3_abort called.
EXT3-fs abort (device ide0(3,5)): ext3_journal_start: Detected aborted
journal
Remounting filesystem read-only
EXT3-fs error (device ide0(3,5)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,5)) in ext3_new_inode: error 28
EXT3-fs error (device ide0(3,5)) in ext3_create: IO failure
EXT3-fs error (device ide0(3,5)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,5)) in start_transaction: Journal has aborted
etc. etc.
-
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 : Thu Nov 07 2002 - 22:00:43 EST