From: Richard Michael <rmichael-raid@edgeofthenet.org>
To: linux-raid@vger.kernel.org
Subject: Docs and operation of RAID10, size limitations on 0.90
Date: Mon, 28 Jul 2008 10:35:53 -0400 [thread overview]
Message-ID: <20080728143553.GE30681@nexus.edgeofthenet.org> (raw)
Hello list,
I'm building a new system with 8 disks, in two RAID5 arrays of 4 disks
each, and a RAID1 array across them. (Then LVM2 on top of the RAID1
array.)
I approached it this way for two reasons:
1/ It feels "cleanest"; in the sense that it's not a special case, it's
just RAID1 with two devices, which happen to be RAID5.
2/ I have a particular usage in mind: I need to be able to split the
mirror and remove half; return it later and resync. Therefore, I want
to know which disks comprise which halves.
However, I'm rethinking toward RAID10. However, I can't find much
documentation about layout, etc. I believe this was recently discussed
on the list.
Can someone with RAID10 experience enlighten me? Can it be cleaned
split, half moved to another host, or rejoined with the first half, etc.
How about performance? (Not a huge issue, but it is better than nested
arrays as I first considered?)
Aside, I'd like it to be bootable. I was told grub only supports
booting from 0.90 superblocks, but that 0.90 has a 2TB limitation?
Meaning, I need /boot with 0.90 and another partition (LVM) with a 1.0
superblocks?
Thanks,
Richard
next reply other threads:[~2008-07-28 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 14:35 Richard Michael [this message]
2008-07-30 16:18 ` Docs and operation of RAID10, size limitations on 0.90 Bill Davidsen
2008-07-30 16:53 ` Richard Michael
2008-07-30 18:29 ` Keld Jørn Simonsen
2008-07-30 21:49 ` Richard Michael
2008-07-30 21:56 ` Jon Nelson
2008-07-30 22:47 ` Richard Michael
2008-07-31 1:11 ` Jon Nelson
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=20080728143553.GE30681@nexus.edgeofthenet.org \
--to=rmichael-raid@edgeofthenet.org \
--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).