xfs
[Top] [All Lists]

Re: 2.6.30-rc6: BUG at fs/xfs/support/debug.c:109!

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: 2.6.30-rc6: BUG at fs/xfs/support/debug.c:109!
From: Alexander Beregalov <a.beregalov@xxxxxxxxx>
Date: Fri, 5 Jun 2009 13:23:38 +0400
Cc: Kernel Testers List <kernel-testers@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=P8B7lxhRcPC/m68ZGdeeQy80wMfuh3vFPGDuoqQ1vaE=; b=couvziYqF/UrGv//oJC8UjPLxkYwhfjJjBWn+TLorCpOr96OAW0PFopJgNNPgnb8Px sSSPDA6duNFrCq2Vth5Tr2b7jAulvVwzhxbW5acvSqJqlYzQ6VlNCjUcy5c6/M+QwsGG yQXHc8ACJ03s3XGAWNpwLpSIt281HhexKb2No=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ubvkiM5dNmgOyUm3rtoXsMpvDHl5U3XXH++rC/mH3m/9E37XvQcBVdjfeo7VYGSMcD Yz7FTIE5ExK7tHoVi5IFu5jffjjUHtifsKkuXm6tM1zuuXP3rcOkQH/Bm9exxdR285QN AtYDYd1i9GjpYowRB0QC35DmCeJABJDvB7cn4=
In-reply-to: <20090604092330.GT16929@xxxxxxxxxxxxxxxx>
References: <a4423d670906010822l6e8e112dl3d6f7de9e2179850@xxxxxxxxxxxxxx> <20090604092330.GT16929@xxxxxxxxxxxxxxxx>
2009/6/4 Dave Chinner <david@xxxxxxxxxxxxx>:
> 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.

<Prev in Thread] Current Thread [Next in Thread>