From: Matt McKenzie <linuxknight@attbi.com>
To: linux-admin@vger.kernel.org
Subject: Re: Recomended IDE-RAID MB
Date: Sun, 06 Apr 2003 15:12:33 -0700 [thread overview]
Message-ID: <3E90A651.5010700@attbi.com> (raw)
In-Reply-To: <3E9038F4.30301.2DC6156@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In my experience where I work, the Tyan motherboards with built in RAID
work well.
Some of them have Promise RAID chip, and the higher end ones have
Adaptec RAID chip, integrated on the motherboard.
I have no throughput test numbers to give.
Andrew B. Cramer wrote:
>Christian,
> Thank you for your input. Just about any speed drive will eat up a T-
>1. I'm just looking for maybe most supported, and reliable. Drives
>are cheap and I will be getting either ATA100 or 133 drives.
>
>Best - Andrew
>
>On 6 Apr 2003 at 11:38, Christian Reis wrote:
>
>
>
>>On Sun, Apr 06, 2003 at 01:00:32AM -0600, Andrew B. Cramer wrote:
>>
>>
>>> What brand of motherboard would you use for just mirroring two huge
>>>IDE drives?
>>>
>>>
>>I'd just make sure the drives were fast, that the MB supported ATA100
>>and that you used 80w IDE cables. My Soyo Dragon Plus gets fairly good
>>throughput; unfortunately, my drives are too slow, which means the total
>>performance would be better than:
>>
>>Version 1.02c ------Sequential Output------ --Sequential Input- --Random-
>> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
>>Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
>>blackjesus 512M 7128 64 8339 6 4925 3 8256 70 13530 5 161.1 0
>> ------Sequential Create------ --------Random Create--------
>> -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>> files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
>> 16 11707 97 +++++ +++ 13882 99 8859 76 +++++ +++ 12141 100
>>
>>In my experience it takes at the most 5 minutes to resync the
>>(on-average) 2GB partitions it is cut up into.
>>
>>This board also includes Promise IDE Hardware RAID, but I've never used
>>it and can't comment on its performance.
>>
>>Take care,
>>--
>>Christian Reis, Senior Engineer, Async Open Source, Brazil.
>>http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
- --
- -----------
73 de K6LNX
Matt M.
LinuxKnight
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
iD8DBQE+kKZS84ta5vs8jhYRArGGAKDUsbfohx+31aN8ZwKeaCsd4wOk9QCgxuiT
/fIvvaBwWRdl3r9Ofq2WvMo=
=gh+2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-04-06 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 7:00 Recomended IDE-RAID MB Andrew B. Cramer
2003-04-06 14:38 ` Christian Reis
2003-04-06 19:25 ` Andrew B. Cramer
2003-04-06 22:12 ` Matt McKenzie [this message]
2003-04-06 23:45 ` Andrew B. Cramer
2003-04-07 13:43 ` Kernel Panic Ben Clewett
2003-04-07 13:48 ` Jamie Harris
2003-04-07 14:22 ` Ben Clewett
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=3E90A651.5010700@attbi.com \
--to=linuxknight@attbi.com \
--cc=linux-admin@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).