From: Andreas Schwab <schwab@suse.de>
To: Jan Niehusmann <jan@gondor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 corruption: "JBD: no valid journal superblock found"
Date: Tue, 01 Nov 2005 18:00:53 +0100 [thread overview]
Message-ID: <jell08qp4q.fsf@sykes.suse.de> (raw)
In-Reply-To: <20051101135123.GB9234@knautsch.gondor.com> (Jan Niehusmann's message of "Tue, 1 Nov 2005 14:51:23 +0100")
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."
prev parent reply other threads:[~2005-11-01 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 13:42 ext3 corruption: "JBD: no valid journal superblock found" Jan Niehusmann
2005-11-01 13:51 ` Jan Niehusmann
2005-11-01 17:00 ` Andreas Schwab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jell08qp4q.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=jan@gondor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.