From: Eric Sandeen <sandeen@sandeen.net>
To: Diane Trout <diane@caltech.edu>, Sean Caron <scaron@umich.edu>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Corrupted file system
Date: Tue, 23 Sep 2014 18:12:33 -0500 [thread overview]
Message-ID: <5421FE61.30508@sandeen.net> (raw)
In-Reply-To: <6825577.fQrC5yyUIR@myrada>
On 9/23/14 5:29 PM, Diane Trout wrote:
> Hello,
>
> Yes, I had my doubts about that there's anything reasonable one could do after
> part of the file system was randomized. I'll trying updating to xfsprogs 3.2.1
> and see if that does any better.
Yes - you didn't mention which version you used, but I'd definitely try something
current. The bug rings a bell, maybe fixed now.
To be safe, you can always make an xfs_metadump image (use -o to not obfuscate
filenames for convenience), xfs_mdrestore that, and point repair at that fs image.
Then you'll see what it *would* do before you *do* do. ;)
But yeah, depending on the damage done to the storage, you may be in trouble
that repair can't help with. Depends on the failure, though.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-23 23:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 22:02 Corrupted file system Diane Trout
2014-09-23 22:12 ` Sean Caron
2014-09-23 22:29 ` Diane Trout
2014-09-23 23:12 ` Eric Sandeen [this message]
2014-09-24 10:08 ` Emmanuel Florac
2014-09-24 20:38 ` Diane Trout
2014-09-24 20:57 ` Eric Sandeen
2014-09-25 0:25 ` Diane Trout
2014-09-25 0:50 ` Eric Sandeen
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=5421FE61.30508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=diane@caltech.edu \
--cc=scaron@umich.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 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.