public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lmcilroy@redhat.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: 2.6.30-rc6: BUG at fs/xfs/support/debug.c:109!
Date: Wed, 1 Jul 2009 21:52:36 -0400 (EDT)	[thread overview]
Message-ID: <584076313.830951246499556455.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <824092896.830901246499419777.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>

Alexander,

Are you running with this fix?

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.29.y.git;a=commitdiff;h=d415867e0abc35e3b2f0d4196e98c339d6fe29a2

I've seen this assertion before and the above patch fixed it
for me.  Hmmm, looks like you're running a recent kernel so
you should have this fix - maybe the fix wasn't quite right.

Lachlan


----- "Alexander Beregalov" <a.beregalov@gmail.com> wrote:

> 2009/6/5 Alexander Beregalov <a.beregalov@gmail.com>:
> > 2009/6/4 Dave Chinner <david@fromorbit.com>:
> >> On Mon, Jun 01, 2009 at 07:22:56PM +0400, Alexander Beregalov
> wrote:
> >>> Hi
> >>>
> >>> Assertion failed: *nmap >= 1, file: fs/xfs/xfs_bmap.c, line: 4846
> >> .....
> >>> Call Trace:
> >>>  [<ffffffff803d6bad>] xfs_bmapi+0xad/0x1ad0
> >>>  [<ffffffff803ee5c0>] xfs_dir2_leaf_getdents+0x640/0x7b0
> >>>  [<ffffffff803e975c>] xfs_readdir+0x12c/0x140
> >>>  [<ffffffff80430b57>] xfs_file_readdir+0x47/0x70
> >>>  [<ffffffff802ec500>] vfs_readdir+0xd0/0xf0
> >>>  [<ffffffff802ec6b6>] sys_getdents+0x96/0x110
> >>>  [<ffffffff8020ba6b>] system_call_fastpath+0x16/0x1b
> >>
> >> I'd say this indicates a corrupted directory.  Can you run
> >> 'xfs_repair -n' over the filesystem and see if it finds a bad
> >> directory?
> 
> Still cannot fix the filesystem. After repairing all corruptions from
> LiveCD it still fails on the same workload.
> 
> Do you need metadump or anything else?
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

       reply	other threads:[~2009-07-02  1:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <824092896.830901246499419777.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-07-02  1:52 ` Lachlan McIlroy [this message]
2009-07-02 10:38   ` 2.6.30-rc6: BUG at fs/xfs/support/debug.c:109! Alexander Beregalov
2009-06-01 15:22 Alexander Beregalov
2009-06-01 16:09 ` Felix Blyakher
2009-06-01 17:38   ` Alexander Beregalov
2009-06-01 17:58     ` Felix Blyakher
2009-06-02  8:21       ` Alexander Beregalov
2009-06-02 11:32         ` Alexander Beregalov
2009-06-01 17:43   ` Alexander Beregalov
2009-06-01 17:53     ` Felix Blyakher
2009-06-04  9:23 ` Dave Chinner
2009-06-05  9:23   ` Alexander Beregalov
2009-07-01 16:21     ` Alexander Beregalov
2009-09-21  3:42 ` Eric Sandeen

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=584076313.830951246499556455.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
    --to=lmcilroy@redhat.com \
    --cc=a.beregalov@gmail.com \
    --cc=kernel-testers@vger.kernel.org \
    --cc=xfs@oss.sgi.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