public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Paul Brunk <pbrunk@uga.edu>, xfs@oss.sgi.com
Subject: Re: rebuilt HW RAID60 array; XFS filesystem looks bad now
Date: Mon, 03 Mar 2014 15:24:32 -0600	[thread overview]
Message-ID: <5314F310.8080703@sandeen.net> (raw)
In-Reply-To: <5314EE97.3020004@uga.edu>

Hi Paul -

On 3/3/14, 3:05 PM, Paul Brunk wrote:
> Hi:

<snip story about very unhappy raid>

It sounds like things are badly scrambled.

> Is there anything I should try prior to xfs_repair -L?

The log failure is probably just the first error xfs encounters;
I imagine that after you zap the log, you'll find that everything
else is in equally bad shape.

You could _try_ an 

# xfs_metadump -o /dev/whatever fs.metadump
# xfs_mdrestore fs.metadump fs.img

and then try your various metadata salvage techniques on fs.img
(recreating as necessary with another xfs_mdrestore after failure)
as practice runs, but I'm guessing that xfs_metadump will fail
in equally spectacular ways.

Unless you can get your storage somehow reassembled properly, I doubt
that there's much xfs tools can do to help you.

-Eric

> I'm just trying to salvage whatever I can from this FS.  I'm aware it
> could be all gone.  Thanks.
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-03-03 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 21:05 rebuilt HW RAID60 array; XFS filesystem looks bad now Paul Brunk
2014-03-03 21:24 ` Eric Sandeen [this message]
2014-03-03 22:53 ` 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=5314F310.8080703@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=pbrunk@uga.edu \
    --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