From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: keld@keldix.com
Cc: NeilBrown <neilb@suse.de>,
Miles Fidelman <mfidelman@meetinghouse.net>,
linux-raid@vger.kernel.org
Subject: Re: possibly silly question (raid failover)
Date: Wed, 02 Nov 2011 09:20:20 +0000 [thread overview]
Message-ID: <4EB10B54.3010808@abpni.co.uk> (raw)
In-Reply-To: <20111102070221.GA24797@www5.open-std.org>
On 02/11/2011 07:02, keld@keldix.com wrote:
> On Wed, Nov 02, 2011 at 12:48:16PM +1100, NeilBrown wrote:
>> On Wed, 2 Nov 2011 02:37:56 +0100 keld@keldix.com wrote:
>>
>>> On Wed, Nov 02, 2011 at 09:25:26AM +1100, NeilBrown wrote:
>>>> On Tue, 1 Nov 2011 23:15:39 +0100 keld@keldix.com wrote:
>>>>
>>>>> On Tue, Nov 01, 2011 at 04:13:26PM -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).
>>>>> In fact raid10 mas a bit less redundancy than raid1+0.
>>>>> It is as far as I know built as raid0+1 with a disk layout
>>>>> where you can only loose eg 1 out of 4 disks, while raid1+0
>>>>> in some cases can loose 2 disks out of 4.
>>>> With md/raid10 you can in some case lose 2 out of 4 disks and survive, just
>>>> like raid1+0.
>>> OK, in which cases, and when is this not the case?
>>>
>>> best regards
>>> keld
>> "just like raid1+0"
> No, that is not the case AFAIK. Eg the layout of raid10,f2 with 4 disks is
> "just like raid0+1".
>
Isn't md raid10 n2 exactly the same as RAID1+0??
next prev parent reply other threads:[~2011-11-02 9:20 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
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 [this message]
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=4EB10B54.3010808@abpni.co.uk \
--to=jonnyt@abpni.co.uk \
--cc=keld@keldix.com \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@meetinghouse.net \
--cc=neilb@suse.de \
/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.