From: Andrew Morton <akpm@osdl.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
sct@redhat.com, adilger@clusterfs.com,
ext2-devel@lists.sourceforge.net
Subject: Re: 2.6.18-mm2: ext3 BUG?
Date: Thu, 5 Oct 2006 17:14:28 -0700 [thread overview]
Message-ID: <20061005171428.636c087c.akpm@osdl.org> (raw)
In-Reply-To: <4525925C.6060807@gmail.com>
On Fri, 06 Oct 2006 01:16:21 +0159
Jiri Slaby <jirislaby@gmail.com> wrote:
> Andrew Morton wrote:
> > On Thu, 05 Oct 2006 23:34:13 +0159
> > Jiri Slaby <jirislaby@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> while yum update-ing, yum crashed and this appeared in log:
> >> [ 2840.688718] EXT3-fs error (device hda2): ext3_free_blocks_sb: bit already
> >> cleared for block 747938
> >> [ 2840.688732] Aborting journal on device hda2.
> >> [ 2840.688858] ext3_abort called.
> >>
> >> ...
> >>
> >> I don't know how to reproduce it and really have no idea what version of -mm
> >> could introduce it (if any).
> >
> > I don't necessarily see a bug in there. The filesystem got a bit noisy but
> > did appropriately detect and handle the metadata inconsistency.
>
> Perhaps, but why did it occur? S.m.a.r.t. doesn't tell me anything suspicious.
Don't know. The usual diagnosis for this sort of thing is "your disk shat
itself". Could be a bad disk, bad power supply, bad memory, some piece of
kernel code went and trashed some memory, bug in the driver. It's a
mystery, sorry.
next prev parent reply other threads:[~2006-10-06 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 21:35 Jiri Slaby
2006-10-05 21:50 ` Andrew Morton
2006-10-05 23:17 ` Jiri Slaby
2006-10-06 0:14 ` Andrew Morton [this message]
2006-10-06 9:33 ` Jiri Kosina
2006-10-08 6:33 ` Jan-Benedict Glaw
2006-10-08 7:14 ` Jan-Benedict Glaw
2006-10-08 8:48 ` Jan-Benedict Glaw
2006-10-08 9:54 ` Jiri Slaby
2006-10-10 7:09 ` Jan-Benedict Glaw
2006-10-11 10:42 ` Jan Kara
2006-10-23 8:13 ` Jan-Benedict Glaw
2006-10-23 10:41 ` Jan Kara
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=20061005171428.636c087c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adilger@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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
Powered by JetHome