From: Jurriaan <thunder7@xs4all.nl>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: 3 disk raid-5 without parity
Date: Mon, 14 Jun 2004 14:42:08 +0200 [thread overview]
Message-ID: <20040614124208.GA5160@middle.of.nowhere> (raw)
In-Reply-To: <16589.36817.228645.72611@cse.unsw.edu.au>
From: Neil Brown <neilb@cse.unsw.edu.au>
Date: Mon, Jun 14, 2004 at 09:45:21PM +1000
> On Monday June 14, thunder7@xs4all.nl wrote:
> > I am trying to convince my boss our new database-server wants raid-0+1,
> > not raid-5, and I got an idea while reading endless articles about
> > raid-5 being slow when writing and management not listening.
>
> You want numbers, not abstract arguments.
>
> Configure your server with raid5 and do some performance measurements
> - preferably with your database suite.
> Then reconfigure with raid 0+1 and test again.
>
> Show the numbers to your boss. You get to choose which numbers to
> show :-)
yes - unfortunately, corporate IT gets to decide which hardware to test
on. Guess what? They just got a shiny new SAN with 140 Gb disks,
configured in raid-5. Not quite the raid-0+1 over 36 Gb disks I had in
mind :-(
Anyway, that was just an introduction - nu use regurgling that on the
list.
> I hope to release a "raid10" module for 2.6 within a couple of weeks.
> raid10 is basically a combination of raid1 and raid0 all in one module
> with some interesting geometry possibilities. This particular
> geometry is one of the possibilities.
>
I'm looking forward to that!
Kind regards,
Jurriaan
--
Anyone can build a fast processor. The trick is to build a fast system.
Seymour Cray
Debian (Unstable) GNU/Linux 2.6.7-rc2-mm2 2x6078 bogomips load 2.49
prev parent reply other threads:[~2004-06-14 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 11:19 3 disk raid-5 without parity Jurriaan
2004-06-14 11:28 ` Brad Campbell
2004-06-14 11:45 ` Neil Brown
2004-06-14 12:42 ` Jurriaan [this message]
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=20040614124208.GA5160@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).