2009/6/5 Alexander Beregalov <[email protected]>:
> 2009/6/4 Dave Chinner <[email protected]>:
>> 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?
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to