Re: ext3 corruption: "JBD: no valid journal superblock found"

[Andreas Schwab <schwab@suse.de>]

Jan Niehusmann <jan@gondor.com> writes:

> On Tue, Nov 01, 2005 at 02:42:33PM +0100, Jan Niehusmann wrote:
>> Currently, I'm experiencing a strange problem with one of my ext3
>> filesystems: There seems to be some journal corruption, but up to now I
>
> Well, of course I forgot one important detail: The kernel version. This
> is a 2.6.14

I'm also experiencing ext3 corruptions with 2.6.14:

Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7): ext3_free_inode: bit already cleared for inode 482170
Oct 29 17:46:08 igel kernel: Aborting journal on device sda7.
Oct 29 17:46:08 igel kernel: ext3_abort called.
Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7): ext3_journal_start_sb: Detected aborted journal
Oct 29 17:46:08 igel kernel: Remounting filesystem read-only
Oct 29 17:46:08 igel kernel: EXT3-fs error (device sda7) in ext3_delete_inode: IO failure

2.6.14-rc5 has been rock solid so far (running on PowerMac G5).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
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/