On Tue, Oct 01, 2013 at 12:57:42PM -0700, Viet Nguyen wrote: > Hi, > > I have a corrupted xfs partition that segfaults when I run xfs_repair, at > the same place every time. > > I'm using the latest version of xfs_repair that I am aware of: xfs_repair > version 3.2.0-alpha1 > > I simply run it as so: xfs_repair -P /dev/sda1 > > Here's a sample of the last few lines that are spit out: > correcting nextents for inode 8637985 > correcting nblocks for inode 8637985, was 198 - counted 0 > correcting nextents for inode 8637985, was 1 - counted 0 > data fork in regular inode 8637987 claims used block 7847452695 > correcting nextents for inode 8637987 > correcting nblocks for inode 8637987, was 198 - counted 0 > correcting nextents for inode 8637987, was 1 - counted 0 > data fork in regular inode 8637999 claims used block 11068974204 > correcting nextents for inode 8637999 > correcting nblocks for inode 8637999, was 200 - counted 0 > correcting nextents for inode 8637999, was 1 - counted 0 > data fork in regular inode 8638002 claims used block 11873152787 > correcting nextents for inode 8638002 > correcting nblocks for inode 8638002, was 201 - counted 0 > correcting nextents for inode 8638002, was 1 - counted 0 > imap claims a free inode 8638005 is in use, correcting imap and clearing > inode > cleared inode 8638005 > imap claims a free inode 8638011 is in use, correcting imap and clearing > inode > cleared inode 8638011 > Segmentation fault (core dumped) > > It crashes after attempting to clear that same inode every time. > > Any advice you can give me on this? Can you run it under gdb and send the stack trace that tells us where it crashed? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
