From: keld@keldix.com
To: d tbsky <tbskyd@gmail.com>
Cc: Reindl Harald <h.reindl@thelounge.net>,
list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid10 redundancy
Date: Sat, 8 May 2021 15:47:26 +0200 [thread overview]
Message-ID: <20210508134726.GA11665@www5.open-std.org> (raw)
In-Reply-To: <CAC6SzH+gZ_WYRdx-vHM6zZxH=kx0YBvV-x2VT9h7EugwdmGcxA@mail.gmail.com>
On Fri, May 07, 2021 at 09:28:35AM +0800, d tbsky wrote:
> Reindl Harald <h.reindl@thelounge.net>
> > Am 06.05.21 um 11:57 schrieb d tbsky:
> > > if losing two disks will madam find out the raid can be rebuilded safely or not?
> >
> > it's pretty simple
> >
> > * if you lose the wrong disks all is gone
> > * if you lsoe the right disks no problem
>
> that's seems reasonable. I will give it a try.
My understanding is that raid10 - all layouts - are really raid0 and then raid 1 on top.
If you loose two disks you loose the whole raid in 2 out of 3 cases in a 4 disk setup.
If it was raid0 over a raid1 you would only lose the whole raid in one out of 3.
raid1
raid0 raid0
d1 d2 d3 d4
gone d1+d2 survives d3+d4
gone d1+d3 dead
gone d1+d4 dead
should be.
raid0
raid1 raid1
d1 d2 d3 d4
gone d1+d2 dead
gone d1+d3 survives
gone d1+d4 survives
keld
next prev parent reply other threads:[~2021-05-08 14:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 5:09 raid10 redundancy d tbsky
2021-05-06 7:48 ` Xiao Ni
2021-05-06 9:57 ` d tbsky
2021-05-06 12:38 ` Reindl Harald
2021-05-07 1:28 ` d tbsky
2021-05-08 13:47 ` keld [this message]
2021-05-09 0:52 ` Phillip Susi
2021-05-12 17:22 ` David T-G
2021-05-12 17:26 ` Reindl Harald
2021-05-12 17:39 ` David T-G
2021-05-13 15:38 ` Andy Smith
2021-05-13 15:46 ` Phillip Susi
2021-05-13 15:59 ` Andy Smith
2021-05-14 14:28 ` Phillip Susi
2021-05-14 14:37 ` Andy Smith
2021-05-17 2:07 ` Brad Campbell
2021-05-06 13:09 ` Phillip Susi
2021-05-07 1:47 ` d tbsky
[not found] ` <86A76859-3098-4AB8-9AE7-46FF54736B88@websitemanagers.com.au>
2021-05-07 3:05 ` d tbsky
2021-05-07 3:26 ` Reindl Harald
2021-05-07 14:53 ` Andy Smith
2021-05-08 1:54 ` d tbsky
2021-05-08 5:55 ` Andy Smith
2021-05-09 1:10 ` Phillip Susi
2021-05-07 1:26 ` d tbsky
2021-05-06 10:39 ` Peter Grandi
2021-05-07 1:37 ` d tbsky
[not found] ` <AD8C004B-FE83-4ABD-B58A-1F7F8683CD1F@websitemanagers.com.au>
2021-05-07 1:12 ` d tbsky
2021-05-07 9:46 ` Wols Lists
2021-05-11 0:04 ` Phil Turmel
2021-05-12 17:27 ` David T-G
2021-05-12 18:20 ` Phil Turmel
2021-05-12 16:31 ` Roy Sigurd Karlsbakk
2021-05-13 15:38 ` Phillip Susi
2021-05-13 18:21 ` Phil Turmel
2021-05-14 14:30 ` Phillip Susi
2021-05-14 14:48 ` Roy Sigurd Karlsbakk
2021-05-17 20:50 ` Phillip Susi
2021-05-17 22:21 ` Wols Lists
2021-05-18 0:12 ` Phil Turmel
2021-05-18 16:05 ` Phillip Susi
2021-05-18 17:38 ` Reindl Harald
2021-05-18 18:51 ` Phillip Susi
2021-05-18 19:02 ` Reindl Harald
2021-05-18 23:48 ` antlists
2021-05-19 3:42 ` Adam Goryachev
2021-05-19 13:02 ` Phillip Susi
2021-05-19 21:19 ` Reindl Harald
2021-05-20 1:32 ` Adam Goryachev
[not found] ` <CAAMCDeeOnraMDNCF6ZZqPAxUrih2gSse1wDYgOfd1LqY-Ffqxw@mail.gmail.com>
2021-05-20 15:08 ` antlists
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=20210508134726.GA11665@www5.open-std.org \
--to=keld@keldix.com \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=tbskyd@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