From: martin f krafft <madduck@madduck.net>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: RAID10: near, far, offset -- which one?
Date: Thu, 5 Oct 2006 17:23:21 +0200 [thread overview]
Message-ID: <20061005152321.GA32017@piper.madduck.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
I am trying to compare the three RADI10 layouts with each other.
Assuming a simple 4 drive setup with 2 copies of each block,
I understand that a "near" layout makes RAID10 resemble RAID1+0
(although it's not 1+0).
I also understand that the "far" layout trades some read performance
for some write performance, so it's best for read-intensive
operations, like read-only file servers.
I don't really understand the "offset" layout. Am I right in
asserting that like "near" it keeps stripes together and thus
requires less seeking, but stores the blocks at different offsets
wrt the disks?
If A,B,C are data blocks, a,b their parts, and 1,2 denote their
copies, the following would be a classic RAID1+0 where 1,2 and 3,4
are RAID0 pairs combined into a RAID1:
hdd1 Aa1 Ba1 Ca1
hdd2 Ab1 Bb1 Cb1
hdd3 Aa2 Ba2 Ca2
hdd4 Ab2 Bb2 Cb2
How would this look with the three different layouts? I think "near"
is pretty much the same as above, but I can't figure out "far" and
"offset" from the md(4) manpage.
Also, what are their respective advantages and disadvantages?
Thanks,
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
"a woman begins by resisting a man's advances and ends by blocking
his retreat."
-- oscar wilde
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-05 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 15:23 martin f krafft [this message]
2006-10-05 17:57 ` RAID10: near, far, offset -- which one? Eli Stair
2006-10-09 23:27 ` Neil Brown
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=20061005152321.GA32017@piper.madduck.net \
--to=madduck@madduck.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).