linux-ext4 - Re: kernel BUG at fs/ext4/extents.c:2738!

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: <1235276519.7599.7.camel@localhost.localdomain>
Date:	Sun, 22 Feb 2009 17:21:59 +1300
From:	Andreas Friedrich Berendsen <afberendsen@...il.com>
To:	Theodore Tso <tytso@....edu>
Cc:	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: kernel BUG at fs/ext4/extents.c:2738!

Tso,

I used fsck many times but an error as identified at a certain block and
fsck was aborting with a Segment fault error. I had to fix all the
errors manually (not using -p or -y), skipping this specific problem.

After that I used reszie2fs -pM for just the first step. Mounting the
filesystem, removing many files (which triggered the BUG), I was able to
run fsck with -y many times.

Anyway, the problem seems to be under control but I'm not sure. The new
kernel (2.6.28.7) has a long list of ext4 errors corrected and I'm
compiling it right now. Let's see what happens next :)

Thanks anyway

-- Andreas

-----Original Message-----
From: Theodore Tso <tytso@....edu>
To: Andreas Friedrich Berendsen <afberendsen@...il.com>
Cc: linux-ext4 <linux-ext4@...r.kernel.org>
Bcc: tytso@....edu
Subject: Re: kernel BUG at fs/ext4/extents.c:2738!
Date: Fri, 20 Feb 2009 14:30:13 -0500

On Sat, Feb 21, 2009 at 07:48:32AM +1300, Andreas Friedrich Berendsen wrote:
> ...I haven't noticed  before, but before that message few more lines
> where recorded, which makes sense with the BUG line. Also, running
> fsck.ext4 on that filesystem I always got a Segment fault at an specific
> point, which it is impossible to fix. I'm in a process to remove files
> from that filesystem, as soon it finish I can run fsck again and send
> the result. Meanwhile, when removing files, rm stuck at a certain inode,
> which caused the first BUG message.

Have you tried running e2fsck?  It sounds like a filesystem corruption
is triggering a BUG() message, which is obviously a bug in and of
itself.  :-)

						- Ted

-- 
__________________________________________
Andreas Friedrich Berendsen
SCA OCP MSCA A+ Linux+ Network+ HpMASE

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html