From: Andrew Morton <akpm@osdl.org>
To: gwingerde@home.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXT-3 bug with 2.6.0-test9
Date: Tue, 25 Nov 2003 12:25:04 -0800 [thread overview]
Message-ID: <20031125122504.47de1ea5.akpm@osdl.org> (raw)
In-Reply-To: <200311252051.15501.gwingerde@home.nl>
Gertjan van Wingerde <gwingerde@home.nl> wrote:
>
> Hi,
>
> (Please CC me in any replies, as I'm not subscribed to the list)
>
> I've just experienced the strange behaviour that my /usr mount auto-magically
> got mounted read-only, where it was mounted read-write (obviously).
> Investigating the cause of this I've found the following EXT-3 related BUG in
> my log-files:
>
> kernel BUG at fs/jbd/journal.c:1733!
Yes. This newly-added BUG check was too easy to trigger and in test10 it
was changed to a printk-and-fix-it-up.
> Nov 25 20:24:20 localhost vmunix: EXT3-fs warning (device md1): ext3_unlink:
> Deleting nonexistent file (230991), 0
> Nov 25 20:24:21 localhost vmunix: EXT3-fs warning (device md1): ext3_unlink:
> Deleting nonexistent file (230990), 0
> Nov 25 20:24:21 localhost vmunix: EXT3-fs warning (device md1): ext3_unlink:
> Deleting nonexistent file (346096), 0
And it is this stuff which triggered the bogus BUG. I do not know why this
happened, but it is probably some form of data loss problem at the md
layer.
It could have happened at any time after the most recent fsck, so if you
have been running earlier kernels on that machine it could even be that the
bug which caused this has already been fixed.
You should run a fsck across all filesystems, and maybe upgrade to test10
plus ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.0-test10-bk1.gz
next prev parent reply other threads:[~2003-11-25 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 19:51 Gertjan van Wingerde
2003-11-25 20:00 ` Mike Fedyk
2003-11-25 20:11 ` Gertjan van Wingerde
2003-11-25 20:25 ` Andrew Morton [this message]
2003-11-26 0:24 ` Gertjan van Wingerde
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=20031125122504.47de1ea5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=gwingerde@home.nl \
--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®