[lkml]   [2006]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.18-mm2: ext3 BUG?
Andrew Morton wrote:
> On Thu, 05 Oct 2006 23:34:13 +0159
> Jiri Slaby <> 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.

> The next step would be to fsck that filesystem, see waht it says.

Yup. I fscked it after reboot and fixed them all...

[went to gather some info from e2fsprogs sources what kind of errors it was (I
didn't note it and can't remember)]

block differences, incorrect block counts, orphaned entries, some (gnome-vfs2
stuff which has been updated) went to lost+found.

I unfotunately can't post more accurate info, because I am a... chump? Bite me
and shame on me...

-- Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-10-06 01:19    [W:0.053 / U:1.604 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site