linux-kernel - Re: 2.6.18-mm2: ext3 BUG?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061005145042.fd62289a.akpm@osdl.org>
Date:	Thu, 5 Oct 2006 14:50:42 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	sct@...hat.com, adilger@...sterfs.com,
	ext2-devel@...ts.sourceforge.net
Subject: Re: 2.6.18-mm2: ext3 BUG?

On Thu, 05 Oct 2006 23:34:13 +0159
Jiri Slaby <jirislaby@...il.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.

The next step would be to fsck that filesystem, see waht it says.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/