public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which linux RAID setup to choose?
Date: Sun, 3 May 2020 16:07:43 -0400	[thread overview]
Message-ID: <CAGfcS_=YyJbCnCwUAi=RYghyf=K1dH98gKnBBbbwBAQJjuV2Qw@mail.gmail.com> (raw)
In-Reply-To: <dri0tBrXDazCGtc_Eu0IwV0R1chgd2giA9ZqGEs8LOJa3vAwAreuXaIR2MeyOgAfXi51yqLcR5NpxDSFY5ss1igKxRAM50hSu7mXY0Y-I78=@protonmail.com>

On Sun, May 3, 2020 at 1:44 AM Caveman Al Toraboran
<toraboracaveman@protonmail.com> wrote:
>
>     * RAID 1: fails to satisfy points (1) and (3)...
> this leaves me with RAID 10

Two things:

1.  RAID 10 doesn't satisfy point 1 (read and write performance are
identical).  No RAID implementation I'm aware of does.

2.  Some RAID1 implementations can satisfy point 3 (expandability to
additional space and replication multiplicities), particular when
combined with LVM.

I'd stop and think about your requirements a bit.  You seem really
concerned about having identical read and write performance.  RAID
implementations all have their pros in cons both in comparison with
each other, in comparison with non-RAID, and in comparison between
read and write within any particular RAID implementation.

I don't think you should focus so much on whether read=write in your
RAID.  I'd focus more on whether read and write both meet your
requirements.

And on that note, what are your requirements?  You haven't mentioned
what you plan to store on it or how this data will be stored or
accessed.  It is hard to say whether any design will meet your
performance requirements when you haven't provided any, other than a
fairly arbitrary read=write one.

In general most RAID1 implementations aren't going to lag regular
non-RAID disk by much and will often exceed it (especially for
reading).  I'm not saying RAID1 is the best option for you - I'm just
suggesting that you don't toss it out just because it reads faster
than it writes, especially in favor of RAID 10 which also reads faster
than it writes but has the additional caveat that small writes may
necessitate an additional read before write.

Not knowing your requirements it is hard to make more specific
recommendations but I'd also consider ZFS and distributed filesystems.
They have some pros and cons around flexibility and if you're
operating at a small scale - it might not be appropriate for your use
case, but you should consider them.

-- 
Rich


  parent reply	other threads:[~2020-05-03 20:08 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
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 [this message]
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='CAGfcS_=YyJbCnCwUAi=RYghyf=K1dH98gKnBBbbwBAQJjuV2Qw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --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