No subject
Wed Nov 21 14:10:37 CST 2012
wasn't able to replay it (and some data loss is acceptable), and then I
mounted the filesystem. This worked! Though it was now showing 22GB used,
all in lost and found. Oops.
I noticed ag 0 reports a lot more free space than any of the others, so I
tried copying sb 1 over sb 0 to get things to use the more intact blocks.
No such luck yet, but I'm definitely getting some data. When I tried using
sb 12, df shows 11T used (about right) but the file list is still very
sparse.
So moving onward! Any recommendations from this point? I take it this is
where I'd run xfs_irecover?
Aaron
On Tue, Nov 13, 2012 at 7:26 PM, Aaron Goulding <aarongldng at gmail.com>wrote:
> Hmm.. Okay new plan. Running XFSB and XAGF scans on /dev/md0 instead of
> /dev/md1, and I'll use that to find the alignment the superblocks are
> expecting, and see if I have an offset wrong somewhere when I ran the
> multi-part DD onto /dev/md1. Barring this, I'll resort to xfs_irecover. I
> think you've given me a lot of information to go on though, so thank you
> greatly.
>
> -Aaron
>
>
>
> On Sun, Nov 11, 2012 at 2:39 PM, Dave Chinner <david at fromorbit.com> wrote:
>
>> On Sat, Nov 10, 2012 at 11:08:23PM -0800, Aaron Goulding wrote:
>> > As I guessed, xfs_repair didn't work. xfs_db does now load with
>> warnings,
>> > but I fear I don't know enough about that to properly use that tool.
>> I've
>> > done a search for xfs_irepair but I'm finding very little from that.
>> Where
>> > is that tool located? I'm understanding a full restore is very unlikely
>> at
>> > this point, but if I can get anything, I'll consider this project a
>> success
>> > and a learning experience. :)
>>
>> xfs_irecover:
>>
>> http://oss.sgi.com/archives/xfs/2008-12/msg01782.html
>>
>> current location:
>>
>> http://inai.de/projects/hxtools/
>>
>> You might need to hack it to recovery full files (ISTR is ignore
>> files larger than a certain size), but tools lke this are your best
>> bet now.
>>
>> Cheers,
>>
>> Dave.
>> --
>> Dave Chinner
>> david at fromorbit.com
>>
>
>
--14dae9cdc0fd136aea04cf46c832
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
So an update! I did another search of /dev/md0 for superblock locations (fi=
nd all instances of XFSB, find all instances of XAGF that occur 512 bytes a=
fter XFSB) and used those as start points to copy the data to /dev/md1. I t=
ook the block count from the superblock, (right at 1TB per AG) and copied t=
hat block of data to the array, properly aligned.<br>
<br>This seems to have worked rather well! xfs_db now has much fewer errors=
, and can read SBs and AGFs, and xfs_repair can do something with it. <br><=
br>From here I did two things. I ran xfs_repair -L to purge the log, as I w=
asn't able to replay it (and some data loss is acceptable), and then I =
mounted the filesystem. This worked! Though it was now showing 22GB used, a=
ll in lost and found. Oops.<br>
<br>I noticed ag 0 reports a lot more free space than any of the others, so=
I tried copying sb 1 over sb 0 to get things to use the more intact blocks=
. No such luck yet, but I'm definitely getting some data. When I tried =
using sb 12, df shows 11T used (about right) but the file list is still ver=
y sparse.<br>
<br>So moving onward! Any recommendations from this point? I take it this i=
s where I'd run xfs_irecover?<br><br>Aaron<br><br><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Tue, Nov 13, 2012 at 7:26 PM, A=
aron Goulding <span dir=3D"ltr"><<a href=3D"mailto:aarongldng at gmail.com"=
target=3D"_blank">aarongldng at gmail.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hmm.. Okay new plan. Running XFSB=A0 and XAG=
F scans on /dev/md0 instead of /dev/md1, and I'll use that to find the =
alignment the superblocks are expecting, and see if I have an offset wrong =
somewhere when I ran the multi-part DD onto /dev/md1. Barring this, I'l=
l resort to xfs_irecover. I think you've given me a lot of information =
to go on though, so thank you greatly.<span class=3D"HOEnZb"><font color=3D=
"#888888"><br>
<br>-Aaron</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br><div cl=
ass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Nov 11, 2012=
at 2:39 PM, Dave Chinner <span dir=3D"ltr"><<a href=3D"mailto:david at fro=
morbit.com" target=3D"_blank">david at fromorbit.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div>On Sat, Nov 10, 2012 at 11:08:23PM=
-0800, Aaron Goulding wrote:<br>
> As I guessed, xfs_repair didn't work. xfs_db does now load with wa=
rnings,<br>
> but I fear I don't know enough about that to properly use that too=
l. I've<br>
> done a search for xfs_irepair but I'm finding very little from tha=
t. Where<br>
> is that tool located? I'm understanding a full restore is very unl=
ikely at<br>
> this point, but if I can get anything, I'll consider this project =
a success<br>
> and a learning experience. :)<br>
<br>
</div></div>xfs_irecover:<br>
<br>
<a href=3D"http://oss.sgi.com/archives/xfs/2008-12/msg01782.html" target=3D=
"_blank">http://oss.sgi.com/archives/xfs/2008-12/msg01782.html</a><br>
<br>
current location:<br>
<br>
<a href=3D"http://inai.de/projects/hxtools/" target=3D"_blank">http://inai.=
de/projects/hxtools/</a><br>
<br>
You might need to hack it to recovery full files (ISTR is ignore<br>
files larger than a certain size), but tools lke this are your best<br>
bet now.<br>
<div><div><br>
Cheers,<br>
<br>
Dave.<br>
--<br>
Dave Chinner<br>
<a href=3D"mailto:david at fromorbit.com" target=3D"_blank">david at fromorbit.co=
m</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
--14dae9cdc0fd136aea04cf46c832--
More information about the xfs
mailing list