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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> wrote:

> 2009/6/5 Alexander Beregalov <a.beregalov@xxxxxxxxx>:
> > 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?
> 
> 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@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux