From: "Jim Buttafuoco" <jim@contactbda.com>
To: Alexander Economou <aecon@gnet.gr>, linux-raid@vger.kernel.org
Subject: Re: SATA Controller
Date: Tue, 10 Aug 2004 09:09:52 -0400 [thread overview]
Message-ID: <20040810130824.M49720@contactbda.com> (raw)
In-Reply-To: <40381.212.251.31.59.1092124213.squirrel@mail.gnet.gr>
I got the 3ware card to do hardware raid at first. The performance we really bad, so I switched to software raid and
while the performance was alot better, it still didn't match other systems I have here that were doing software raid
with older IDT (parallel) disks.
Jim
---------- Original Message -----------
From: "Alexander Economou" <aecon@gnet.gr>
To: linux-raid@vger.kernel.org
Sent: Tue, 10 Aug 2004 10:50:13 +0300 (EEST)
Subject: Re: SATA Controller
> 0
>
> If you plan on using software raid it would be a nice idea to use a 2.6.x
> kernel in case you are using a 2.4.x kernel.There is a huge speed diff in
> data transfer between those 2 kernel versions.
> I have installed a couple of s150 tx4 and i can say that they work fine.I
> also noticed that there is support for this controller in the low level
> driver section(scsi) in 2.4.27 kernel.If this doesnt work out (wich i
> doubt it)try downloading the driver from promise.com.
> One thing i dont understand is why buy raid controllers and do software
> raid(if that is what you ment)
>
> > All,
> >
> > I am thinking of going with the following SATA PCI controller (non raid)
> > to replace my 3ware SATA controller (only
> > using JBOD but thats another story). Any comments on linux support /
> > issues / other controllers you have luck with.
> > I am planning on using software raid with 3 of these cards and 10 250G WD
> > SATA disks.
> >
> > Thanks
> > Jim
> >
> > PROMISE PCI to SATA Controller Card, Model "SATA150 TX4" -OEM
> >
> > Model# Sata150 TX4
> > Item # N82E16816102013
> >
> > Specifications:
> > Ports: 4x Serial ATA/150
> > OS Support: Windows 98/Me/NT4/2000/XP; RedHat 7.3/8.0; SuSE 7.3/8.0
> > Feature: Bus mastering offloads data I/O handling from host CPU; CRC
> > error-checking of Serial ATA and Ultra ATA drives for data reliability
> > during transfers; Data Transfer Rate:150MB/sec with Serial ATA/150 drives,
> > 133MB/sec with Ultra ATA/133 drives, 100MB/sec with Ultra ATA/100 drives;
> > 32-bit 33/66MHz PCI bus; PCI 2.3 compliant
> > -
> > 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
> >
>
> --
> Alexander Economou
> GNET NOC
> -
> 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
------- End of Original Message -------
prev parent reply other threads:[~2004-08-10 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:53 SATA Controller Jim Buttafuoco
2004-08-10 7:50 ` Alexander Economou
2004-08-10 13:09 ` Jim Buttafuoco [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=20040810130824.M49720@contactbda.com \
--to=jim@contactbda.com \
--cc=aecon@gnet.gr \
--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).