linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: RAID10, 3 copies, 3 disks
Date: Sat, 11 Jan 2020 21:25:35 +0000	[thread overview]
Message-ID: <5E1A3D4F.30205@youngman.org.uk> (raw)
In-Reply-To: <CAJH6TXji3e1Tp8xDDiqfqy36fpMC4kZTLaYj0Le9A6Cyg8EnGg@mail.gmail.com>

On 11/01/20 20:55, Gandalf Corvotempesta wrote:
> Il giorno sab 11 gen 2020 alle ore 20:11 Wol
> <antlists@youngman.org.uk> ha scritto:
>> The "standard" as you call it is actually RAID1+0. This is *not* "linux
>> raid10", which is as you describe it - the number of disks can be any
>> number greater than the number of mirrors.
> 
> Actually, what I need to do is simple: a scalable array with at least
> 3way-mirrors.
> 
> I've thought in using multiple 3way mirrors (RAID1) merged together with LVM or
> just a single RAID10 (with 3 disks mirrors) and LVM on top of it as
> volume manager.
> 
> Don't know which one is better, the result is similar.
> 
Multiple 3-way mirrors (1+0) requires disks in multiples of 3. Raid10
simply requires "4 or more" disks. If you expect/want to expand your
storage in small increments, then 10 is clearly better. BUT.

Depending on your filesystem - for example XFS - changing the disk
layout underneath it can severely impact performance - when the
filesystem is created it queries the layout and optimises for it. When I
discussed it with one of the XFS guys he said "use 1+0 and add a fresh
*set* of disks (or completely recreate the filesystem), because XFS
optimises layout based on what disks it thinks its got."

Cheers,
Wol

  reply	other threads:[~2020-01-11 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11  7:06 RAID10, 3 copies, 3 disks Gandalf Corvotempesta
     [not found] ` <82a7d9ec-f991-ad25-bf1f-eee74be90b1b@youngman.org.uk>
2020-01-11 20:55   ` Gandalf Corvotempesta
2020-01-11 21:25     ` Wols Lists [this message]
2020-01-11 21:36       ` Gandalf Corvotempesta
2020-01-14 12:28         ` Nix

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=5E1A3D4F.30205@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=linux-raid@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).