From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Alex Davis <alex14641@yahoo.com>
Cc: Kasper Sandberg <lkml@metanurb.dk>,
David Greaves <david@dgreaves.com>,
David Lethe <david@santools.com>, David Rees <drees76@gmail.com>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sharing disks amoung multiple software RAIDs
Date: Sat, 3 May 2008 12:13:02 +0200 [thread overview]
Message-ID: <20080503101302.GB10819@rap.rap.dk> (raw)
In-Reply-To: <824925.21830.qm@web50201.mail.re2.yahoo.com>
On Fri, May 02, 2008 at 05:44:18PM -0700, Alex Davis wrote:
>
>
> I code, therefore I am
>
>
> --- On Fri, 5/2/08, David Lethe <david@santools.com> wrote:
> [snipped]
> > I was being too literal. md is a good solution (I use it
> > myself). However, the OP wanted to "Make sure that if
> > one disk dies, the data is still in tact".
> I was also concerned about performance. It seems that if the RAIDs will
> be used heavily and independent of each other, and performance is a
> concern, then dedicated disks (and possibly dedicated controllers)
> are the better option.
My understanding of having multiple, possibly differnet types of RAID
partitions say on two drives, are that performance-wise this are the
same considerations as for a single drive. You can worry about head
movement and seek times and transfer rates, but the problems are the
same for raid and non-raid. IMHO architecturally multiple RAIDs on same disks
do not introduce additional performance issues compared with single disk
solutions, nor with one-raid-per-set-of-drives solutions.
The above statement on having separate disks per raid is more or less the
same as saying that the more disks you have, the better.
If performance is an issue, then I am recommending my pet
raid10,f2 layout, which has a 30 - 80 % increased performance over
traditional RAID1, because it uses only the outer faster tracks on the
disk, and it has reduced seek time only searching on half of the disk
(and this the again the outer part, so that the head movement is reduced
to about 1/3).
Best regards
keld
next prev parent reply other threads:[~2008-05-03 10:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 11:35 Sharing disks amoung multiple software RAIDs 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 8:36 George Spelvin
2008-05-02 11:07 ` Alex Davis
2008-05-02 13:26 ` Richard Michael
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=20080503101302.GB10819@rap.rap.dk \
--to=keld@dkuug.dk \
--cc=alex14641@yahoo.com \
--cc=david@dgreaves.com \
--cc=david@santools.com \
--cc=drees76@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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).