From: "George Spelvin" <linux@horizon.com>
To: alex14641@yahoo.com
Cc: linux@horizon.com, linux-raid@vger.kernel.org
Subject: Re: Sharing disks amoung multiple software RAIDs
Date: Fri, 02 May 2008 04:36:55 -0400 [thread overview]
Message-ID: <20080502083656.28029.qmail@science.horizon.com> (raw)
Can you explain what you mean, exactly?
Do you just mean having two partitions on the same drive used as part
of other RAID arrays? That works fine.
Having two heavilty used partitions on the same drive causes some
performance issues, but no correctness ones. And there's nothing
special about RAID for this consideration; it would apply with
non-RAID partitions as well.
But I have mirrored swap striped across all drives; I don't
use swap a lot and it's not worth getting dedicated drives.
Likewise, /boot is a 6-way RAID-1 emergency rescue partition.
I can boot off any drive, and I have a basic text-mode install
with all the disaster recovery tools. Again, not heavily used.
If you're doing serious database work, it's common to split the
system, log, and database across different spindles. But that's
independent of whether RAID is used for any of them.
But there are other possible interpretations of "sharing among multiple
RAIDs", like hot spares and the like. Could you be more specific?
Obviously, having the same partition active in multiple different
arrays would be an unmitigated disaster, but I don't think you mean that.
(And I don't think mdadm lets you do it, either.)
One thing that's very nice about Linux software RAID is that you *don't*
have to RAID whole drives. It took me a while to understand Intel's
"Matrix RAID" feature because it had never occurred to me that a RAID
array *couldn't* be set up that way.
next reply other threads:[~2008-05-02 8:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 8:36 George Spelvin [this message]
2008-05-02 11:07 ` Sharing disks amoung multiple software RAIDs Alex Davis
2008-05-02 13:26 ` Richard Michael
-- strict thread matches above, loose matches on Subject: below --
2008-05-01 11:35 Alex Davis
2008-05-01 12:50 ` Justin Piszcz
2008-05-01 13:42 ` Alex Davis
2008-05-02 21:24 ` Bill Davidsen
2008-05-02 1:39 ` Kasper Sandberg
2008-05-02 1:51 ` Alex Davis
2008-05-02 2:31 ` David Lethe
2008-05-02 2:42 ` Kasper Sandberg
2008-05-02 7:06 ` David Rees
2008-05-02 8:09 ` Kasper Sandberg
2008-05-02 8:25 ` David Greaves
2008-05-02 21:43 ` Kasper Sandberg
2008-05-02 22:04 ` Alex Davis
2008-05-02 22:24 ` David Lethe
2008-05-03 0:44 ` Alex Davis
2008-05-03 10:13 ` Keld Jørn Simonsen
2008-05-03 3:11 ` Kasper Sandberg
2008-05-02 10:25 ` Keld Jørn Simonsen
[not found] ` <481E0726.1030501@harddata.com>
[not found] ` <20080504212927.GB20650@rap.rap.dk>
[not found] ` <481E3374.4070105@harddata.com>
2008-05-04 23:10 ` Keld Jørn Simonsen
2008-05-04 23:17 ` Keld Jørn Simonsen
2008-05-02 13:43 ` Helge Hafting
2008-05-02 14:13 ` Alex Davis
2008-05-01 12:51 ` David Greaves
2008-05-02 1:23 ` Nick Andrew
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=20080502083656.28029.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=alex14641@yahoo.com \
--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).