[Top] [All Lists]

Re: Partially corrupted raid array beneath xfs

To: Christopher Evans <christophere@xxxxxxxxxxxxxxxxx>
Subject: Re: Partially corrupted raid array beneath xfs
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 25 Jan 2012 11:49:54 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <CAO4DVWoqgswvcSWii9uy6zuFyczVGQXFJjbgPi4XiMx+5cw2cA@xxxxxxxxxxxxxx>
References: <CAO4DVWoqgswvcSWii9uy6zuFyczVGQXFJjbgPi4XiMx+5cw2cA@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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 ;)


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>