From: Ross Vandegrift <ross@willow.seitz.com>
To: "Peter L. Ashford" <ashford@sdsc.edu>
Cc: Jonathan Vardy <jonathan@explainerdc.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RAID 5 performance problems
Date: Thu, 3 Apr 2003 13:47:56 -0500 [thread overview]
Message-ID: <20030403184756.GA7971@willow.seitz.com> (raw)
In-Reply-To: <Pine.GSO.4.30.0304030858080.20118-100000@multivac.sdsc.edu>
[CC list trimmed]
On Thu, Apr 03, 2003 at 10:05:27AM -0800, Peter L. Ashford wrote:
> > 4 of the raid HD's are connected to the Promise controller and the other
> > raid HD is master on the second onboard IDE channel (udma2/ATA33)
>
> I've NEVER heard that the FastTrak runs fast (I have been told that they
> run VERY slowly).
The FastTrack cards are identical to the UltraDMA cards from promise -
you can turn one into the other with a resistor and a firmware flash.
> I've benchmarked RAW disk speeds with an Ultra-100 and
> WD1200JB drives, and gotten 50MB/S from each disk, as opposed to your
> 26MB/S (there should be almost no difference for the BB drives).
Makes perfect sense - he's getting 50M/s to each channel, but it's split
over two drives, so drive throughput is about halved.
> Use one disk per channel
> (Master only), and move the system disk onto one of the Promise cards.
Absolutely correct - you should *never* run IDE RAID on a channel that
has both a master and slave. When one disk on an IDE channel has an
error, the whole channel is reset - this makes both disks inaccessible,
and RAID5 now has two failed disks => you data is gone! *ALWAYS* use
separate IDE channels.
--
Ross Vandegrift
ross@willow.seitz.com
A Pope has a Water Cannon. It is a Water Cannon.
He fires Holy-Water from it. It is a Holy-Water Cannon.
He Blesses it. It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it. It is a Wholly Holy Holy-Water Cannon.
He has it pierced. It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official. It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive. He shoots them.
next prev parent reply other threads:[~2003-04-03 18:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 15:45 RAID 5 performance problems Jonathan Vardy
2003-04-03 18:05 ` Peter L. Ashford
2003-04-03 18:47 ` Ross Vandegrift [this message]
2003-04-03 19:22 ` Stephan van Hienen
2003-04-03 19:20 ` Stephan van Hienen
2003-04-03 19:28 ` Alan Cox
2003-04-03 21:02 ` Ezra Nugroho
2003-04-03 21:25 ` Stephan van Hienen
2003-04-03 21:38 ` Peter L. Ashford
2003-04-03 22:09 ` Jonathan Vardy
2003-04-03 22:16 ` Jonathan Vardy
2003-04-03 22:28 ` Peter L. Ashford
2003-04-03 21:42 ` Jonathan Vardy
2003-04-03 22:13 ` Peter L. Ashford
2003-04-03 21:06 ` Felipe Alfaro Solana
2003-04-03 21:14 ` Jonathan Vardy
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 19:13 Neil Schemenauer
2003-04-03 19:49 Andy Arvai
2003-04-03 20:25 ` Mike Dresser
2003-04-03 21:10 ` Jonathan Vardy
2003-04-03 21:31 ` Ezra Nugroho
2003-04-04 11:44 Jonathan Vardy
2003-04-04 14:39 ` Ezra Nugroho
2003-04-04 15:05 Jonathan Vardy
2003-04-04 16:01 Jonathan Vardy
2003-04-05 0:10 ` Jonathan Vardy
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=20030403184756.GA7971@willow.seitz.com \
--to=ross@willow.seitz.com \
--cc=ashford@sdsc.edu \
--cc=jonathan@explainerdc.com \
--cc=linux-kernel@vger.kernel.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).