From: Miles Fidelman <mfidelman@meetinghouse.net>
To: linux-raid@vger.kernel.org
Subject: Re: possibly silly question (raid failover)
Date: Tue, 01 Nov 2011 17:32:17 -0400 [thread overview]
Message-ID: <4EB06561.8090706@meetinghouse.net> (raw)
In-Reply-To: <20111101212023.GA20565@cthulhu.home.robinhill.me.uk>
Robin Hill wrote:
> On Tue Nov 01, 2011 at 04:13:26 -0400, Miles Fidelman wrote:
>
>> David Brown wrote:
>>> No, md RAID10 does /not/ offer more redundancy than RAID1. You are
>>> right that md RAID10 offers more than RAID1 (or traditional RAID0 over
>>> RAID1 sets) - but it is a convenience and performance benefit, not a
>>> redundancy benefit. In particular, it lets you build RAID10 from any
>>> number of disks, not just two. And it lets you stripe over all disks,
>>> improving performance for some loads (though not /all/ loads - if you
>>> have lots of concurrent small reads, you may be faster using plain
>>> RAID1).
>> wasn't suggesting that it does - just that it does things differently
>> than normal raid 1+0 - for example, by doing mirroring and striping as a
>> unitary operation, it works across odd number of drives - it also (I
>> think) allows for more than 2 copies of a block (not completely clear
>> how many copies of a block would be made if you specified a 16 drive
>> array) - sort of what I'm wondering here
>>
> By default it'll make 2 copies, regardless how many devices are in the
> array. You can specify how many copies you want though, so -n3 will give
> you a near configuration with 3 copies, -n4 for four copies, etc.
>
>
cool, so with 16 drives, and say -n6 or -n8, and a far configuration -
that gives a pretty good level of resistance to multi-disk failures, as
well as an entire node failure (taking out 4 drives)
which then leaves the question of whether the md driver, itself, can be
failed over from one node to another
Thanks!
Miles
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
next prev parent reply other threads:[~2011-11-01 21:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 0:38 possibly silly question (raid failover) Miles Fidelman
2011-11-01 9:14 ` David Brown
2011-11-01 13:05 ` Miles Fidelman
2011-11-01 13:37 ` John Robinson
2011-11-01 14:36 ` David Brown
2011-11-01 20:13 ` Miles Fidelman
2011-11-01 21:20 ` Robin Hill
2011-11-01 21:32 ` Miles Fidelman [this message]
2011-11-01 21:50 ` Robin Hill
2011-11-01 22:35 ` Miles Fidelman
2011-11-01 22:00 ` David Brown
2011-11-01 22:58 ` Miles Fidelman
2011-11-02 10:36 ` David Brown
2011-11-01 22:15 ` keld
2011-11-01 22:25 ` NeilBrown
2011-11-01 22:38 ` Miles Fidelman
2011-11-02 1:40 ` keld
2011-11-02 1:37 ` keld
2011-11-02 1:48 ` NeilBrown
2011-11-02 7:02 ` keld
2011-11-02 9:20 ` Jonathan Tripathy
2011-11-02 11:27 ` David Brown
2011-11-01 9:26 ` Johannes Truschnigg
2011-11-01 13:02 ` Miles Fidelman
2011-11-01 13:33 ` John Robinson
2011-11-02 6:41 ` Stan Hoeppner
2011-11-02 13:17 ` Miles Fidelman
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=4EB06561.8090706@meetinghouse.net \
--to=mfidelman@meetinghouse.net \
--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.