From: Eric Sandeen <sandeen@sandeen.net>
To: Richard Kolkovich <richard@intrameta.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfs_repair: catch bad depth in traverse_int_dir2block
Date: Thu, 11 Jun 2009 17:30:52 -0500 [thread overview]
Message-ID: <4A31859C.2090209@sandeen.net> (raw)
In-Reply-To: <20090610214750.GB39123@divination.intrameta.com>
Richard Kolkovich wrote:
> On Tue, Jun 09, 2009 at 12:38:35PM -0400, Eric Sandeen wrote:
>> Richard Kolkovich wrote:
>>> Guys,
>>>
>>> After applying the patch, we get much further. xfs_repair then fails in phase 7:
>>>
>>>
>>> xfs_repair: phase7.c:47: set_nlinks: Assertion `fs_inode_nlink' failed.
>>>
>>> Aborted
>>>
>>>
>>> Any ideas on that one? Thanks!
>> Yep, I meant to reply, I hit that one too. Haven't yet looked into that
>> one ....
>>
>> -Eric
>
> Any ideas on a workaround if not a fix? We really just want to get through the repair and see what
> (if anything) is still usable...
Try setting the nlink feature on the superblock, which apparently got
lost... i'm not sure why repair doesn't cope but you can fix that:
xfs_db -x /device
xfs_db> sb 0
xfs_db> write versionnum 0x30A4
but then you'll hit something else I'm looking at, an inode moved to
lost+found which is still not referenced, grr.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-11 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 3:51 [PATCH] xfs_repair: catch bad depth in traverse_int_dir2block Eric Sandeen
2009-06-08 7:42 ` Christoph Hellwig
2009-06-09 16:06 ` Richard Kolkovich
2009-06-09 16:38 ` Eric Sandeen
2009-06-10 21:47 ` Richard Kolkovich
2009-06-11 22:30 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A31859C.2090209@sandeen.net \
--to=sandeen@sandeen.net \
--cc=richard@intrameta.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox