From: Dave Chinner <david@fromorbit.com>
To: Aaron Goulding <aarongldng@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem recovery from secondary superblocks
Date: Mon, 12 Nov 2012 09:39:44 +1100 [thread overview]
Message-ID: <20121111223944.GN24575@dastard> (raw)
In-Reply-To: <CABJyUzJ7maOcj+aPkpCvBc1-P+Z-XPsft8rbsVnqgpfyVCs9xQ@mail.gmail.com>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-11 22:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 5:02 XFS filesystem recovery from secondary superblocks Aaron Goulding
2012-11-01 9:18 ` Emmanuel Florac
2012-11-01 22:59 ` Dave Chinner
2012-11-07 15:24 ` Aaron Goulding
[not found] ` <CABJyUz+r7yQSswqyBng_W=fAXxTz9heb88NeiKSeFU7j4ZD=Hw@mail.gmail.com>
2012-11-08 21:02 ` Dave Chinner
[not found] ` <CABJyUzKy4YXVZAj=awVNfPD69eWo2mKhM7a-xWF1Vy-PD989sg@mail.gmail.com>
2012-11-09 10:48 ` Dave Chinner
2012-11-09 15:22 ` Aaron Goulding
2012-11-11 7:08 ` Aaron Goulding
2012-11-11 22:39 ` Dave Chinner [this message]
2012-11-14 3:26 ` Aaron Goulding
2012-11-25 0:20 ` Aaron Goulding
2012-11-11 22:36 ` Dave Chinner
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=20121111223944.GN24575@dastard \
--to=david@fromorbit.com \
--cc=aarongldng@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.