From: Dave Chinner <david@fromorbit.com>
To: Christopher Evans <christophere@luma-pictures.com>
Cc: xfs@oss.sgi.com
Subject: Re: Partially corrupted raid array beneath xfs
Date: Wed, 25 Jan 2012 11:49:54 +1100 [thread overview]
Message-ID: <20120125004954.GQ15102@dastard> (raw)
In-Reply-To: <CAO4DVWoqgswvcSWii9uy6zuFyczVGQXFJjbgPi4XiMx+5cw2cA@mail.gmail.com>
On Tue, Jan 24, 2012 at 09:59:09AM -0800, Christopher Evans wrote:
> I made a mistake by recreating a raid 6 array, instead of taking the proper
> steps to rebuild it. Is there a way I can get find out which directories,
> files are/might be corrupted if 64k blocks of data offset every 21 times
> for an unknown count. Unfortunetly I've already mounted the raid array and
> have gotten xfs errors because of the corrupted data beneath it.
Write a script that walks the filesystem run xfs_bmap on every file
and directory and work out which one have extents that fall into the
bad range. If you walk into a corrupted directory, then you're
likely to see errors in dmesg, too.
In future we'll have a reverse mapping tree that will enable use to
avoid the tree walk to find the owners of corrupted regions like
this. I wrote half the code for it while I was at LCA last week ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-01-25 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 17:59 Partially corrupted raid array beneath xfs Christopher Evans
2012-01-25 0:49 ` Dave 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=20120125004954.GQ15102@dastard \
--to=david@fromorbit.com \
--cc=christophere@luma-pictures.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