From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which linux RAID setup to choose?
Date: Sun, 3 May 2020 10:14:13 +0100 [thread overview]
Message-ID: <5EAE8B65.8070501@youngman.org.uk> (raw)
In-Reply-To: <dri0tBrXDazCGtc_Eu0IwV0R1chgd2giA9ZqGEs8LOJa3vAwAreuXaIR2MeyOgAfXi51yqLcR5NpxDSFY5ss1igKxRAM50hSu7mXY0Y-I78=@protonmail.com>
On 03/05/20 06:44, Caveman Al Toraboran wrote:
> hi - i'm to setup my 1st RAID, and i'd appreciate
> if any of you volunteers some time to share your
> valuable experience on this subject.
>
> my scenario
> -----------
>
> 0. i don't boot from the RAID.
>
> 1. read is as important as write. i don't
> have any application-specific scenario that
> makes me somehow favor one over another.
> so RAIDs that speed up the read (or write)
> while significantly harming the write (or
> read) is not welcome.
>
> 2. replacing failed disks may take a week or
> two. so, i guess that i may have several
> disks fail one after another in the 1-2
> weeks (specially if they were bought
> about the same time).
>
> 3. i would like to be able to grow the RAID's
> total space (as needed), and increase its
> reliability (i.e. duplicates/partities) as
> needed.
>
> e.g. suppose that i got a 2TB RAID that
> tolerates 1 disk failure. i'd like to, at
> some point, to have the following options:
>
> * only increase the total space (e.g.
> make it 3TB), without increasing
> failure toleration (so 2 disk failure
> would result in data loss).
>
> * or, only increase the failure tolerance
> (e.g. such that 2 disks failure would
> not lead to data loss), without
> increasing the total space (e.g. space
> remains 2TB).
>
> * or, increase, both, the space and the
> failure tolerance at the same time.
>
> 4. only interested in software RAID.
>
> my thought
> ----------
>
> i think these are not suitable:
>
> * RAID 0: fails to satisfy point (3).
>
> * RAID 1: fails to satisfy points (1) and (3).
>
> * RAIDs 4 to 6: fails to satisfy point (3)
> since they are stuck with a fixed tolerance
> towards failing disks (i.e. RAIDs 4 and 5
> tolerate only 1 disk failure, and RAID 6
> tolerates only 2).
>
>
> this leaves me with RAID 10, with the "far"
> layout. e.g. --layout=n2 would tolerate the
> failure of two disks, --layout=n3 three, etc. or
> is it? (i'm not sure).
>
> my questions
> ------------
>
> Q1: which RAID setup would you recommend?
I'd recommend having a spare in the array. That way, a single failure
would not affect redundancy at all. You can then replace the spare at
your leisure.
If you want to grow the array, I'd also suggest "raid 5 + spare". That's
probably better than 6 for writing. but 6 is better than 5 for
redundancy. Look at having a journal - that could speed up write speed
for raid 6.
>
> Q2: how would the total number of disks in a
> RAID10 setup affect the tolerance towards
> the failing disks?
>
Sadly, it doesn't. If you have two copies, losing two disks COULD take
out your raid.
> if the total number of disks is even, then
> it is easy to see how this is equivalent
> to the classical RAID 1+0 as shown in
> md(4), where any disk failure is tolerated
> for as long as each RAID1 group has 1 disk
> failure only.
That's a gamble ...
>
> so, we get the following combinations of
> disk failures that, if happen, we won't
> lose any data:
>
> RAID0
> ------^------
> RAID1 RAID1
> --^-- --^--
> F . . . < cases with
> . F . . < single disk
> . . F . < failures
> . . . F <
>
> F . . F < cases with
> . F F . < two disk
> . F . F < failures
> F . F . <
> . F F . <
>
> this gives us 4+5=9 possible disk failure
> scenarious where we can survive it without
> any data loss.
>
> but, when the number of disks is odd, then
> written bytes and their duplicates will
> start wrap around, and it is difficult for
> me to intuitively see how would this
> affect the total number of scenarious
> where i will survive a disk failure.
>
> Q3: what are the future growth/shrinkage
> options for a RAID10 setup? e.g. with
> respect to these:
>
> 1. read/write speed.
iirc far is good for speed.
> 2. tolerance guarantee towards failing
> disks.
Guarantees? If you have two mirrors. the guarantee is just ONE disk. Yes
you can gamble on losing more.
> 3. total available space.
iirc you can NOT grow the far layout.
>
> rgrds,
> cm.
>
You have looked at the wiki - yes I know I push it regularly :-)
https://raid.wiki.kernel.org/index.php/Linux_Raid
Cheers,
Wol
next prev parent reply other threads:[~2020-05-03 9:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 5:44 [gentoo-user] which linux RAID setup to choose? Caveman Al Toraboran
2020-05-03 7:53 ` hitachi303
2020-05-03 9:23 ` Wols Lists
2020-05-03 17:55 ` Caveman Al Toraboran
2020-05-03 18:04 ` Dale
2020-05-03 18:29 ` Mark Knecht
2020-05-03 20:16 ` Rich Freeman
2020-05-03 22:52 ` Mark Knecht
2020-05-03 23:23 ` Rich Freeman
2020-05-03 21:22 ` antlists
2020-05-03 9:14 ` Wols Lists [this message]
2020-05-03 9:21 ` Caveman Al Toraboran
2020-05-03 14:27 ` Jack
2020-05-03 21:46 ` Caveman Al Toraboran
2020-05-03 22:50 ` hitachi303
2020-05-04 0:29 ` Caveman Al Toraboran
2020-05-04 7:50 ` hitachi303
2020-05-04 0:46 ` Rich Freeman
2020-05-04 7:50 ` hitachi303
2020-05-04 8:18 ` William Kenworthy
2020-05-03 23:19 ` antlists
2020-05-04 1:33 ` Caveman Al Toraboran
2020-05-03 20:07 ` Rich Freeman
2020-05-03 21:32 ` antlists
2020-05-03 22:34 ` Rich Freeman
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=5EAE8B65.8070501@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.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