All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Fidelman <mfidelman@meetinghouse.net>
To: linux-raid@vger.kernel.org
Subject: Re: wish for Linux MD mirrored raid types
Date: Fri, 06 May 2011 12:23:12 -0400	[thread overview]
Message-ID: <4DC42070.2070401@meetinghouse.net> (raw)
In-Reply-To: <BANLkTik8A0szuNk2HvDqQXpY3tSAdPoUKA@mail.gmail.com>

Roberto Spadim wrote:
> hum, i asked this question one time, the point is:
> raid1 code is very easy
> raid10 code is more complex
>
> easy = faster, less memory, less cpu
> complex = faster?, more memory? more cpu?
>
> check others raid system (freebsd, netbsd) and check how they do...
>
> 2011/5/6 Keld Jørn Simonsen<keld@keldix.com>:
>    
>>> Keld Jørn Simonsen wrote:
>>>        
>>>>> As you say, RAID10,near on four disks is pretty much identical to
>>>>> RAID1+0 - i.e., a stripe of two normal RAID1 pairs.
>>>>>
>>>>>            

of course RAID10 offers the far option, and the option to run on an odd 
number of drives (I currently use it on a couple of 4-drive servers, but 
as I  look at some replacement hardware I've been thinking that RAID10 
on a 5-drive configuration offers a nice mix of reliability and performance)

re. easy/complex - I'm not sure I really believe that - when I've 
reviewed options, I come to the conclusion that:

RAID1 - wastes a lot of drive space, particularly if you want to 
maintain reliability after a single-drive failure (requires a minimum of 
3 mirrored drives)

RAID5 and RAID6 are better when it comes to mixing efficiency with 
multi-drive failures, but have a couple of odd failure modes and are a 
real pain to rebuild after a failure

RAID1+0 and RAID0+1 are interesting combination - but my sense is that 
every time you nest a layer, you're adding configuration complexity, 
processing delays (low level cpu cycles and i/o transactions), and just 
that much more complexity if you have to reconfigure or rebuild and 
array (particularly if you're running LVM and DRBD on top of the basic 
disk arrays, as I am)

md RAID10 chops out a layer of nesting and makes better use of disk 
space - by combining block replication and striping into a single layer 
- providing what, to me, is a good balance of disk use, multiple copies 
of data, performance, and managability - so far, its worked well for me



-- 
In theory, there is no difference between theory and practice.
In<fnord>  practice, there is.   .... Yogi Berra


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-06 16:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  7:17 wish for Linux MD mirrored raid types Keld Jørn Simonsen
2011-05-06  7:31 ` Roman Mamedov
2011-05-06  9:03   ` Keld Jørn Simonsen
2011-05-06  9:22     ` Jonathan Tripathy
2011-05-06  9:41       ` Keld Jørn Simonsen
2011-05-06  9:50         ` Roman Mamedov
2011-05-06 10:05           ` Jonathan Tripathy
2011-05-06 10:54             ` David Brown
2011-05-06 13:27               ` Keld Jørn Simonsen
2011-05-06 14:01                 ` Miles Fidelman
2011-05-06 15:24                   ` Keld Jørn Simonsen
2011-05-06 15:34                     ` Roberto Spadim
2011-05-06 16:23                       ` Miles Fidelman [this message]
2011-05-06 18:29                       ` Keld Jørn Simonsen
2011-05-06 20:30                 ` Leslie Rhorer
2011-05-06 20:43                   ` Miles Fidelman
2011-05-06 12:33           ` Keld Jørn Simonsen
2011-05-06 13:26             ` Mikael Abrahamsson
2011-05-06 13:40               ` Keld Jørn Simonsen
2011-05-06  7:51 ` David Brown
2011-05-06  9:27   ` Keld Jørn Simonsen
2011-05-08 18:14 ` Luca Berra
2011-05-08 21:25   ` Miles Fidelman
2011-05-09  3:40     ` Keld Jørn Simonsen
2011-05-09  4:24       ` NeilBrown
2011-05-09 19:57         ` Keld Jørn Simonsen
2011-05-09  5:22 ` Emmanuel Noobadmin
2011-05-09 14:48   ` Roberto Spadim
2011-05-09 19:59   ` Keld Jørn Simonsen
2011-05-09 20:12     ` Roberto Spadim

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=4DC42070.2070401@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.