All of lore.kernel.org
 help / color / mirror / Atom feed
From: David T-G <davidtg-robot@justpickone.org>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: what's wrong with RAID-10?
Date: Mon, 27 Jun 2022 11:23:13 -0400	[thread overview]
Message-ID: <20220627152313.GO18273@justpickone.org> (raw)
In-Reply-To: <d058da47-528e-f9af-dbb1-5941eef72b56@youngman.org.uk>

Wol, et al --

...and then Wols Lists said...
% 
% On 27/06/2022 11:41, David T-G wrote:
% > 
% > ...and then Wols Lists said...
% > %
% > % Bummer. It's a raid-10. A raid-1 would have been easier.
% > [snip]
% > 
...
% > 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.

OH!!  That helps.  I was bummer-ing the wrong aspect and trying to
figure out why RAID-10 was a bad design choice.  Now i get it :-)


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

Yeah.


% 
% Cheers,
% Wol


Thanks again!

:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt


  reply	other threads:[~2022-06-27 15:23 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
2022-06-27 15:23         ` David T-G [this message]
2022-06-27 18:41         ` 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=20220627152313.GO18273@justpickone.org \
    --to=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.