linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Friedrich Berendsen <afberendsen@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: kernel BUG at fs/ext4/extents.c:2738!
Date: Fri, 20 Feb 2009 14:40:31 -0600	[thread overview]
Message-ID: <499F153F.2000502@redhat.com> (raw)
In-Reply-To: <1235155713.22702.25.camel@localhost.localdomain>

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.

please stop w/ the file removal for a moment, and see if you can make an
e2image of the filesystem which reproduces the e2fsck problem ....

-Eric

  parent reply	other threads:[~2009-02-20 20:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  7:40 kernel BUG at fs/ext4/extents.c:2738! Andreas Friedrich Berendsen
2009-02-20 15:42 ` Eric Sandeen
2009-02-20 18:48   ` Andreas Friedrich Berendsen
2009-02-20 19:30     ` Theodore Tso
2009-02-22  4:21       ` Andreas Friedrich Berendsen
2009-02-22  4:31         ` Theodore Tso
2009-02-22  5:22           ` Andreas Friedrich Berendsen
2009-02-22 20:00             ` Theodore Tso
2009-02-20 20:40     ` Eric Sandeen [this message]
2009-02-20 21:56       ` Andreas Friedrich Berendsen

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=499F153F.2000502@redhat.com \
    --to=sandeen@redhat.com \
    --cc=afberendsen@gmail.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).