From: Chris Mason <chris.mason@oracle.com>
To: Travis Shivers <ttshivers@gmail.com>
Cc: cwillu <cwillu@cwillu.com>, Gurudas Pai <gurudas.pai@oracle.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs Storage Array Corrupted
Date: Wed, 29 Feb 2012 17:14:14 -0500 [thread overview]
Message-ID: <20120229221414.GS5054@shiny> (raw)
In-Reply-To: <CAPeorG9u6Z-Z5QnxAc5QB3ZzrR17+3Y2t-UQFd8v_aqN-rVwTA@mail.gmail.com>
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
next prev parent reply other threads:[~2012-02-29 22:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:13 Btrfs Storage Array Corrupted Travis Shivers
2012-02-29 0:34 ` Fajar A. Nugraha
2012-02-29 1:41 ` Gurudas Pai
2012-02-29 2:50 ` Chris Mason
2012-02-29 3:00 ` Travis Shivers
2012-02-29 3:16 ` cwillu
2012-02-29 3:36 ` Travis Shivers
2012-02-29 13:59 ` Chris Mason
2012-02-29 21:57 ` Travis Shivers
2012-02-29 22:14 ` Chris Mason [this message]
2012-02-29 23:11 ` Travis Shivers
2012-02-29 23:44 ` Chris Mason
2012-02-29 23:58 ` Travis Shivers
2012-03-16 17:30 ` Travis Shivers
[not found] ` <CAPeorG-Zrr-fTaYmHHKQ5=0jL9ZqjbTypGzo7je3g=MJDPmXcA@mail.gmail.com>
2012-03-26 23:15 ` Travis Shivers
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=20120229221414.GS5054@shiny \
--to=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=gurudas.pai@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ttshivers@gmail.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;
as well as URLs for NNTP newsgroup(s).