public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: Dave Chinner <david@fromorbit.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: Fri, 5 Jun 2009 13:23:38 +0400	[thread overview]
Message-ID: <a4423d670906050223p4e72ceaaqa1dd942a2e52d1a3@mail.gmail.com> (raw)
In-Reply-To: <20090604092330.GT16929@discord.disaster>

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?

Hi Dave

It is a rootfs. xfs_repair found and fixed all errors, but after
reboot the problem still persists (but at another stage of running
`emerge`).

localhost ~ # echo s > /proc/sysrq-trigger
localhost ~ # echo s > /proc/sysrq-trigger
localhost ~ # echo u > /proc/sysrq-trigger
localhost ~ # xfs_repair -nd /dev/sda2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 4
        - agno = 3
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

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

  reply	other threads:[~2009-06-05  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
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 [this message]
2009-07-01 16:21     ` Alexander Beregalov
2009-09-21  3:42 ` Eric Sandeen
     [not found] <824092896.830901246499419777.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-07-02  1:52 ` Lachlan McIlroy
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=a4423d670906050223p4e72ceaaqa1dd942a2e52d1a3@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=david@fromorbit.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