From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Hiroshi Honda <xero@incoming.jp>, Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Unable to rescue RAID5
Date: Fri, 14 Oct 2016 07:28:03 -0400 [thread overview]
Message-ID: <0b965ca4-014b-33f2-295b-a02feb0d7ccb@gmail.com> (raw)
In-Reply-To: <20161014191141.2154.13A92CCA@incoming.jp>
On 2016-10-14 06:11, Hiroshi Honda wrote:
>> That's the proper answer. In practice... all hope isn't yet lost.
> I understood the proper answer.
> I'll take care it in the future.
>
> Is there something step/method can I do from this situation?
>
You should probably look at `btrfs restore`. I'm not sure how well it
works with the raid56 code, and you'll need somewhere to put the data
being restored, but that's probably your best option.
next prev parent reply other threads:[~2016-10-14 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 1:28 Unable to rescue RAID5 Hiroshi Honda
2016-10-14 2:47 ` Duncan
2016-10-14 10:11 ` Hiroshi Honda
2016-10-14 11:28 ` Austin S. Hemmelgarn [this message]
2016-10-16 2:34 ` Hiroshi Honda
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=0b965ca4-014b-33f2-295b-a02feb0d7ccb@gmail.com \
--to=ahferroin7@gmail.com \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=xero@incoming.jp \
/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).