Re: Btrfs Storage Array Corrupted

[Chris Mason <chris.mason@xxxxxxxxxx>]

On Wed, Feb 29, 2012 at 03:57:19PM -0600, Travis Shivers wrote:
> Here is the output from the commands:
> 
> # ./btrfs-debug-tree -R /dev/sdh
> failed to read /dev/sr0: No medium found
> failed to read /dev/sde: No medium found
> failed to read /dev/sdd: No medium found
> failed to read /dev/sdc: No medium found
> failed to read /dev/sdb: No medium found
> failed to read /dev/sda: No medium found
> parent transid verify failed on 5568194695168 wanted 43477 found 43151

So far all the blocks that have come up look like they are in the extent
allocation tree.  This helps because it is the easiest to recover.

I can also make a patch for you against 3.3-rc that skips reading it
entirely, which should make it possible to copy things off.

But before I do that, could you describe the raid array?  Was it
mirrored or raid10?  What exactly happened when it stopped working?

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html