From: Dave Chinner <david@fromorbit.com>
To: Leslie Rhorer <lrhorer@mygrande.net>
Cc: xfs@oss.sgi.com
Subject: Re: Corrupted files
Date: Wed, 10 Sep 2014 08:06:45 +1000 [thread overview]
Message-ID: <20140909220645.GH20518@dastard> (raw)
In-Reply-To: <540F1B01.3020700@mygrande.net>
On Tue, Sep 09, 2014 at 10:21:37AM -0500, Leslie Rhorer wrote:
>
> Hello,
>
> I have an issue with my primary RAID array. I have 13T of data on
> the array, and I suffered a major array failure. I was able to
> rebuild the array, but some data was lost. Of course I have
> backups, so after running xfs_repair, I ran an rsync job to recover
> the lost data. Most of it was recovered, but there are several
> files that cannot be read, deleted, or overwritten. I have tried
> running xfs_repair several times, but any attempt to access these
> files continuously reports "cannot stat XXXXXXXX: Structure needs
> cleaning". I don't need to try to recover the data directly, as it
> does reside on the backup, but I need to clear the file structure so
> I can write the files back to the filesystem. How do I proceed?
Fristly, more infomration is required, namely versions and actual
error messages:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
dmesg, in particular, should tell use what the corruption being
encountered is when stat fails.
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:[~2014-09-09 22:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:21 Corrupted files Leslie Rhorer
2014-09-09 15:50 ` Sean Caron
2014-09-09 16:03 ` Sean Caron
2014-09-09 22:24 ` Eric Sandeen
2014-09-09 22:57 ` Sean Caron
2014-09-10 1:00 ` Roger Willcocks
2014-09-10 1:23 ` Leslie Rhorer
2014-09-10 5:09 ` Eric Sandeen
2014-09-10 0:48 ` Leslie Rhorer
2014-09-10 1:10 ` Roger Willcocks
2014-09-10 1:31 ` Leslie Rhorer
2014-09-10 14:24 ` Emmanuel Florac
2014-09-10 14:49 ` Sean Caron
2014-09-09 16:08 ` Emmanuel Florac
2014-09-09 22:06 ` Dave Chinner [this message]
2014-09-10 1:12 ` Leslie Rhorer
2014-09-10 1:25 ` Sean Caron
2014-09-10 1:43 ` Leslie Rhorer
2014-09-10 14:31 ` Emmanuel Florac
2014-09-10 14:52 ` Grozdan
2014-09-10 15:12 ` Emmanuel Florac
2014-09-10 15:32 ` Grozdan
2014-09-10 14:54 ` Sean Caron
2014-09-10 23:18 ` Leslie Rhorer
2014-09-11 13:24 ` Greg Freemyer
2014-09-12 7:06 ` Emmanuel Florac
2014-09-10 1:53 ` Dave Chinner
2014-09-10 3:10 ` Leslie Rhorer
2014-09-10 3:33 ` Dave Chinner
2014-09-10 4:14 ` Leslie Rhorer
2014-09-10 4:22 ` Leslie Rhorer
2014-09-10 14:34 ` Emmanuel Florac
2014-09-10 4:51 ` Leslie Rhorer
2014-09-10 5:23 ` Dave Chinner
2014-09-11 5:47 ` Leslie Rhorer
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=20140909220645.GH20518@dastard \
--to=david@fromorbit.com \
--cc=lrhorer@mygrande.net \
--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