From: Dave Chinner <david@fromorbit.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: Thu, 4 Jun 2009 19:23:30 +1000 [thread overview]
Message-ID: <20090604092330.GT16929@discord.disaster> (raw)
In-Reply-To: <a4423d670906010822l6e8e112dl3d6f7de9e2179850@mail.gmail.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?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-04 9:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 15:22 2.6.30-rc6: BUG at fs/xfs/support/debug.c:109! Alexander Beregalov
[not found] ` <a4423d670906010822l6e8e112dl3d6f7de9e2179850-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-01 16:09 ` Felix Blyakher
[not found] ` <B5660F1A-7940-4E4A-92E8-8C0F93C274BD-sJ/iWh9BUns@public.gmane.org>
2009-06-01 17:38 ` Alexander Beregalov
[not found] ` <a4423d670906011038qd809ebay22aebca5aaf271a4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-01 17:58 ` Felix Blyakher
[not found] ` <D7FB8214-6C2B-4D13-9B50-C53CB74885C2-sJ/iWh9BUns@public.gmane.org>
2009-06-02 8:21 ` Alexander Beregalov
2009-06-02 11:32 ` Alexander Beregalov
2009-06-01 17:43 ` Alexander Beregalov
[not found] ` <a4423d670906011043v52426cb9s547547479b5f885d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-01 17:53 ` Felix Blyakher
2009-09-21 3:42 ` Eric Sandeen
2009-06-04 9:23 ` Dave Chinner [this message]
[not found] ` <20090604092330.GT16929-CJ6yYqJ1V6CgjvmRZuSThA@public.gmane.org>
2009-06-05 9:23 ` Alexander Beregalov
[not found] ` <a4423d670906050223p4e72ceaaqa1dd942a2e52d1a3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-01 16:21 ` Alexander Beregalov
[not found] <824092896.830901246499419777.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
[not found] ` <824092896.830901246499419777.JavaMail.root-rwXUz/BPrj9+R5eDjrG6zsCp5Q1pQRjfhaY/URYTgi6ny3qCrzbmXA@public.gmane.org>
2009-07-02 1:52 ` Lachlan McIlroy
[not found] ` <584076313.830951246499556455.JavaMail.root-rwXUz/BPrj9+R5eDjrG6zsCp5Q1pQRjfhaY/URYTgi6ny3qCrzbmXA@public.gmane.org>
2009-07-02 10:38 ` Alexander Beregalov
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=20090604092330.GT16929@discord.disaster \
--to=david@fromorbit.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