From: Wols Lists <antlists@youngman.org.uk>
To: d tbsky <tbskyd@gmail.com>,
Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: list Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid10 redundancy
Date: Fri, 7 May 2021 10:46:35 +0100 [thread overview]
Message-ID: <60950C7B.5040706@youngman.org.uk> (raw)
In-Reply-To: <CAC6SzHKH62XwudewxtOUyNQYi9QSFar=dZ64fz9HiEW1eZh47g@mail.gmail.com>
On 07/05/21 02:12, d tbsky wrote:
> Adam Goryachev <mailinglists@websitemanagers.com.au>
>>
>> I guess it depends on your definition of raid 10... In my experience it means one or more raid 1 arrays combine with raid 0, so if each raid 1 arrays had 2 members, then it is either 2, 4, 6, etc for the total number of drives.
>
> indeed. What I want to use is linux raid10 which can be used on
> 2,3,4,5, etc of disk drives. so it is unlike hardware raid 10.
>
If you're worried about losing two drives, okay it's more disk space,
but add the third drive and go for three copies. Then adding the fourth
drive will give you extra space. Not the best but heigh ho.
Or make sure you've got a spare drive configured, so if one drive fails
the array will rebuild immediately, and your window of danger is minimised.
Cheers,
Wol
next prev parent reply other threads:[~2021-05-07 9:48 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
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 [this message]
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=60950C7B.5040706@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--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