2.5.46 ext3 errors

From: Jens Axboe (axboe@suse.de)
Date: Wed Nov 06 2002 - 02:54:06 EST

Next message: chrisl@vmware.com: "[PATCH] Fix bug in ext3 htree rename: doesn't delete old name, leaves ino with bad nlink"
Previous message: Eric W. Biederman: "Re: [lkcd-devel] Re: What's left over."
Next in thread: Jens Axboe: "Re: 2.5.46 ext3 errors"
Reply: Jens Axboe: "Re: 2.5.46 ext3 errors"
Reply: Maciej Babinski: "Re: 2.5.46 ext3 errors"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

Doing a kernel compile, the file system suddenly turned read-only.
Following messages appeared in log:

EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count corrupted in group 688 Aborting journal on device ide1(22,1).
ext3_new_inode: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide1(22,1)) in ext3_new_inode: Journal has aborted
EXT3-fs error (device ide1(22,1)) in ext3_create: Journal has aborted ext3_abort called.
EXT3-fs abort (device ide1(22,1)): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only

-- Jens Axboe

- 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/

Next message: chrisl@vmware.com: "[PATCH] Fix bug in ext3 htree rename: doesn't delete old name, leaves ino with bad nlink"
Previous message: Eric W. Biederman: "Re: [lkcd-devel] Re: What's left over."
Next in thread: Jens Axboe: "Re: 2.5.46 ext3 errors"
Reply: Jens Axboe: "Re: 2.5.46 ext3 errors"
Reply: Maciej Babinski: "Re: 2.5.46 ext3 errors"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:42 EST