From: Bill Davidsen <davidsen@tmr.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Marc Perkel <mperkel@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Raid 10 question/problem [ot]
Date: Mon, 29 Jan 2007 10:17:44 -0500 [thread overview]
Message-ID: <45BE1018.4010402@tmr.com> (raw)
In-Reply-To: <45BCFE33.3000600@tls.msk.ru>
Michael Tokarev wrote:
> Bill Davidsen wrote:
> []
>> RAID-10 is not the same as RAID 0+1.
>
> It is. Yes, there's separate module for raid10, but what it - basically -
> does is the same as raid0 module over two raid1 modules will do. It's
> just a bit more efficient (less levels, more room for optimisations),
> easy to use (you'll have single array instead of at least 3), and a bit
> more flexible; at the same way it's less widely tested...
>
> But the end result is basically the same for both ways.
>
For values of "same" which exclude consideration of the disk layout,
throughput, overhead, system administration, and use of spares. Those
are different. But both methods do write multiple copies of ones and
zeros to storage media.
Neil brown, 08/23/2005:
- A raid10 can consist of an odd number of drives (if you have a
cabinet with, say, 8 slots, you can have 1 hot spare, and 7 drives
in a raid10. You cannot do that with LVM (or raid0) over raid1).
- raid10 has a layout ('far') which theoretically can provide
sequential read throughput that scales by number of drives, rather
than number of raid1 pairs. I say 'theoretically' because I think
there are still issues with the read-balancing code that make this
hard to get in practice (though increasing the read-ahead seems to
help).
After about 40 configurations tested, I can say that write performance
is better as well, for any given stripe cache size up to 4x stripe size.
I was looking at something else, but the numbers happen to be available.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2007-01-29 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 18:00 Raid 10 question/problem [ot] Marc Perkel
2007-01-27 18:09 ` Jan Engelhardt
2007-01-27 18:31 ` Marc Perkel
2007-01-27 18:32 ` Jan Engelhardt
2007-01-27 18:42 ` Marc Perkel
2007-01-27 20:59 ` Jan Engelhardt
2007-01-27 18:52 ` Marc Perkel
2007-01-28 9:05 ` Michael Tokarev
2007-01-28 12:40 ` Jan Engelhardt
2007-01-28 19:44 ` Michael Tokarev
2007-01-28 21:45 ` Jan Engelhardt
2007-01-28 17:38 ` Bill Davidsen
2007-01-28 19:49 ` Michael Tokarev
2007-01-28 21:40 ` Jan Engelhardt
2007-01-29 15:17 ` Bill Davidsen [this message]
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=45BE1018.4010402@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=mperkel@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox