From: Rik Herrin <rikherrin@yahoo.com>
To: Lajber Zoltan <lajbi@lajli.gau.hu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Linux RAID Enterprise-Level Capabilities and If It Supports Raid Level Migration and Online Capacity Expansion
Date: Thu, 29 Dec 2005 03:30:32 -0800 (PST) [thread overview]
Message-ID: <20051229113032.23937.qmail@web52909.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0512221625480.13179@lajli.gau.hu>
Thanks Lajber. Sorry for taking so long to reply but
it's been a busy week. Your test benchmarks look
interesting. Do they take into consideration the
random seeks that Molle mentioned in his email? As
Molle mentioned: "I've seen lots of MD tests, but none
that covered profiling MD's random access
performance". Does this cover MD's random access
performance?
Also, have you thought of using iometer
(http://www.iometer.org) and comparing it's results
with bonnie++'s results? Just a thought...
Thanks for your time...
--- Lajber Zoltan <lajbi@lajli.gau.hu> wrote:
> Hi,
>
> On Thu, 22 Dec 2005, Rik Herrin wrote:
>
> > 1) OCE: Online Capacity Expansion: From the
> latest
> > version of mdadm (v2.2), it ssems that there is
> > support for it with the -G option. How well
> tested is
>
> Well, we use LVM above raid, thins is not a big
> issue.
>
> > 3) Performance issues: I'm currently thinking of
>
> I have some simple test with bonnie++, the sw raid
> superior to hw raid,
> except big-name storage systems.
> http://zeus.gau.hu/~lajbi/diskbenchmarks.txt
>
> > 4) Would anyone recommend a certain hotswap
> > enclosure?
>
> We used ibm xseries and sun machines. The hotswap
> working well, but the
> number of drives very limited.
>
> Take a look at http://www.coraid.com : very well
> scalable, cheap storage.
>
> Bye,
>
-=Lajbi=----------------------------------------------------------------
> LAJBER Zoltan Szent Istvan Egyetem,
> Informatika Hivatal
> Most of the time, if you think you are in trouble,
> crank that throttle!
>
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-12-29 11:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 10:07 Linux RAID Enterprise-Level Capabilities and If It Supports Raid Level Migration and Online Capacity Expansion Rik Herrin
2005-12-22 12:31 ` Molle Bestefich
2005-12-22 15:06 ` Ross Vandegrift
2005-12-22 15:20 ` Molle Bestefich
2005-12-29 11:20 ` Rik Herrin
2005-12-29 18:20 ` H. Peter Anvin
2005-12-22 15:29 ` Lajber Zoltan
2005-12-22 15:36 ` Molle Bestefich
2005-12-22 15:57 ` Lajber Zoltan
2005-12-29 11:30 ` Rik Herrin [this message]
2005-12-22 21:37 ` Robert Heinzmann
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 17:07 Andrew Burgess
2005-12-22 20:15 ` John Stoffel
2005-12-22 23:02 ` Lajber Zoltan
2005-12-27 6:46 ` jeane
2005-12-27 6:55 ` Lajber Zoltan
2006-01-04 1:39 ` Dan Stromberg
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=20051229113032.23937.qmail@web52909.mail.yahoo.com \
--to=rikherrin@yahoo.com \
--cc=lajbi@lajli.gau.hu \
--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).