From: Wolfgang Mader <Wolfgang_Mader@brain-frog.de>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Likelihood of read error, recover device failure raid10
Date: Sat, 13 Aug 2016 17:39:18 +0200 [thread overview]
Message-ID: <2336793.AMaAIAxWk4@discus> (raw)
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Hi,
I have two questions
1) Layout of raid10 in btrfs
btrfs pools all devices and than stripes and mirrors across this pool. Is it
therefore correct, that a raid10 layout consisting of 4 devices a,b,c,d is
_not_
raid0
|---------------|
------------ -------------
|a| |b| |c| |d|
raid1 raid1
Rather, there is no clear distinction of device level between two devices
which form a raid1 set which are than paired by raid0, but simply, each bit is
mirrored across two different devices. Is this correct?
2) Recover raid10 from a failed disk
Raid10 inherits its redundancy from the raid1 scheme. If I build a raid10 from
n devices, each bit is mirrored across two devices. Therefore, in order to
restore a raid10 from a single failed device, I need to read the amount of
data worth this device from the remaining n-1 devices. In case, the amount of
data on the failed disk is in the order of the number of bits for which I can
expect an unrecoverable read error from a device, I will most likely not be
able to recover from the disk failure. Is this conclusion correct, or am I am
missing something here.
Thanks,
Wolfgang
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-08-13 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 15:39 Wolfgang Mader [this message]
2016-08-13 20:15 ` Likelihood of read error, recover device failure raid10 Hugo Mills
2016-08-14 1:07 ` Duncan
2016-08-14 16:20 ` Chris Murphy
2016-08-14 18:04 ` Wolfgang Mader
2016-08-15 4:21 ` Wolfgang Mader
2016-08-15 3:46 ` Andrei Borzenkov
2016-08-15 5:51 ` Andrei Borzenkov
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=2336793.AMaAIAxWk4@discus \
--to=wolfgang_mader@brain-frog.de \
--cc=linux-btrfs@vger.kernel.org \
/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).