All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: David T-G <davidtg-robot@justpickone.org>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: what's wrong with RAID-10? (was "Re: moving a working array")
Date: Mon, 27 Jun 2022 16:10:45 +0100	[thread overview]
Message-ID: <d058da47-528e-f9af-dbb1-5941eef72b56@youngman.org.uk> (raw)
In-Reply-To: <20220627104109.GJ18273@justpickone.org>

On 27/06/2022 11:41, David T-G wrote:
> Wol, et al --
> 
> ...and then Wols Lists said...
> %
> % On 24/06/2022 15:09, Wilson Jonathan wrote:
> % > On Fri, 2022-06-24 at 08:38 -0500, o1bigtenor wrote:
> % > >
> % > > I have a working (no issues) raid-10 array in one box.
> %
> % Bummer. It's a raid-10. A raid-1 would have been easier.
> [snip]
> 
> This tripped me.  I presumed that the reason for -10, not least because
> he also said "these 4 drives", was because the array space is bigger than
> just one hard drive size, ie 6T on 4ea 3T drives.  How would RAID-1 work
> for that storage?  And why would it be easier than RAID-10?
> 
Just that raid-1 would have been a simple case of two drives, each a 
backup of the other. Keep one safe, put the other in the new system.

With raid-10, it's much more complicated - you can't just do that :-(

Cheers,
Wol

  reply	other threads:[~2022-06-27 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 13:38 moving a working array o1bigtenor
2022-06-24 14:09 ` Wilson Jonathan
2022-06-24 14:49   ` Wols Lists
2022-06-27 10:41     ` what's wrong with RAID-10? (was "Re: moving a working array") David T-G
2022-06-27 15:10       ` Wols Lists [this message]
2022-06-27 15:23         ` what's wrong with RAID-10? David T-G
2022-06-27 18:41         ` what's wrong with RAID-10? (was "Re: moving a working array") Reindl Harald
2022-06-27 18:52           ` Wols Lists
2022-06-27 23:37             ` Reindl Harald

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=d058da47-528e-f9af-dbb1-5941eef72b56@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=davidtg-robot@justpickone.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.