From: David Chinner <dgc@sgi.com>
To: Jeffrey Sandel <JSandel@ortivawireless.com>
Cc: xfs@oss.sgi.com
Subject: Re: Recovering Data From Lost+Found
Date: Thu, 10 Apr 2008 10:16:51 +1000 [thread overview]
Message-ID: <20080410001651.GN108924158@sgi.com> (raw)
In-Reply-To: <720665D03D82304C98BA1EEDCE3EA6FE7A206C@exchange01.ortivawireless.com>
On Wed, Apr 09, 2008 at 11:25:28AM -0700, Jeffrey Sandel wrote:
> Last week we ran a firmware upgrade on a Coraid box with the drives
> mounted. The firmware upgrade corrupted part of the data and caused
> input output errors for users trying to acess the NFS mount. We then
> repaired the xfs file system with xfs_repair and all of the data was
> dumped into the lost+found directory without filenames or ownership of
> the files displayed, only inode numbers. I want to restore the data to
> it's oiginal state before the firmware upgrade and before the xfs
> _repair. Is there a command in xfs that you can do this with.
Please check the archives before posting questions. There is a current
thread on exactly this topic. You'll find the answer there....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-04-10 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 18:25 Recovering Data From Lost+Found Jeffrey Sandel
2008-04-10 0:16 ` David Chinner [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=20080410001651.GN108924158@sgi.com \
--to=dgc@sgi.com \
--cc=JSandel@ortivawireless.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