xfs_repair will do some good. After running xfs_repair the xfs_check script will no longer trigger a SEGV of xfs_db.
But xfs_repair will never get the filesystem to a state whereby xfs_check finds no errors. I've run xfs_repair many times and xfs_check always gives the following error afterwards: link count mismatch for inode 37806328 (name ?), nlink 7, counted 6 Also no matter how many times I run it xfs_repair gives me a heap of "disconnected inode 62936029, moving to lost+found" messages (with the same inode numbers as far as I can tell from a quick visual scan). I'll give the entire image to people in SGI Melbourne, next week probably. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
