From: Andrew Morton <akpm@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc1-mm2 - 'journal block not found' - ext3 on crack?
Date: Fri, 3 Sep 2004 16:48:24 -0700 [thread overview]
Message-ID: <20040903164824.4a3b0ee1.akpm@osdl.org> (raw)
In-Reply-To: <200409021815.i82IFpLT022145@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>
> I built 2.6.9-rc1-mm2 last night, and I've had this happen on 2 separate file systems today:
>
> Sep 2 12:42:50 turing-police kernel: journal_bmap: journal block not found at offset 2316 on dm-6
> Sep 2 12:42:52 turing-police kernel: Aborting journal on device dm-6.
> Sep 2 12:42:52 turing-police kernel: ext3_abort called.
> Sep 2 12:42:53 turing-police kernel: EXT3-fs error (device dm-6): ext3_journal_start: Detected aborted journal
> Sep 2 12:42:53 turing-police kernel: Remounting filesystem read-only
> Sep 2 12:42:54 turing-police kernel: EXT3-fs error (device dm-6) in start_transaction: Journal has aborted
> Sep 2 12:42:54 turing-police kernel: EXT3-fs error (device dm-6) in start_transaction: Journal has aborted
> Sep 2 12:42:54 turing-police kernel: journal commit I/O error
> Sep 2 12:42:54 turing-police kernel: EXT3-fs error (device dm-6) in start_transaction: Journal has aborted
> Sep 2 12:42:57 turing-police last message repeated 15 times
>
> (This one was /home - I'd paste the other one, but it happened on /var so
> it didn't get logged because /var/adm/messages went R/O..)
Probably caused by an I/O error (or data loss) performing metadata reads.
> Of interest:
>
> 1) Didn't see this under 2.6.8-mm4.
> 2) Neither time had any actual disk I/O error messages...
> 3) I'm using ext3-on-LVM, if that matters...
Let me guess: raid5?
We've had a steady stream of heisenbugreports for ext3-on-raid5
for several years.
next prev parent reply other threads:[~2004-09-03 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 18:15 Valdis.Kletnieks
2004-09-03 23:48 ` Andrew Morton [this message]
2004-09-05 12:00 ` karl.vogel
2004-09-13 8:25 ` Valdis.Kletnieks
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=20040903164824.4a3b0ee1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Valdis.Kletnieks@vt.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®