From: "Rev. Jeffrey Paul" <sneak@datavibe.net>
To: David Rees <dbr@greenhydrant.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: experiences with 3Ware 6400 3W-6400?
Date: Fri, 27 Jun 2003 09:24:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0306270920010.6883@datavibe.net> (raw)
In-Reply-To: <1908.66.75.244.69.1056697569.squirrel@www.greenhydrant.com>
On Fri, 27 Jun 2003, David Rees wrote:
> Maurice Hilarius said:
> >>Rev. Jeffrey Paul said:
> >> >
> >> > I'm thinking of buying one of these for a production server that I'm
> >> > setting up. Has anyone had any experiences with these on linux, good
> >> > or bad?
> >
> > Why would you buy a 2 year old, nearly unsupported card?
> > ?Heck I can sell you 8 port 3W-7810 cards for under $300
> > And they work really well in software RAID.
>
> I was going to mention the same thing in my post, but forgot. I didn't
> think that you could buy the 6400 new anymore, so where are you getting
> them from? The 7500 runs about $250 which is a bit expensive for real
> low-budget servers.
>
> -Dave
I'd done some quick searches for "3ware" on ebay, having heard good things
about their ide-raid cards. The 7xxx series are too expensive for the
project I'm working on at the moment. It's either an older card, or
software RAID1 (and, with all due respect, I don't want to use linux
software raid in -this sort- of production environment).
Are the 6xxx series really that bad? I don't care about 'nearly'
unsupported, just as long as it works. My budget for this whole project
is likely less than $500.
We're currently looking at raid1 across two 80-120GB disks for a samba
file server in an office that does a lot of graphic design.
-j
--
--------------------------------------------------------
Rev. Jeffrey Paul -datavibe- sneak@datavibe.net
aim:x736e65616b pgp:0x15FA257E phone:8777483467
70E0 B896 D5F3 8BF4 4BEE 2CCF EF2F BA28 15FA 257E
--------------------------------------------------------
next prev parent reply other threads:[~2003-06-27 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 20:57 experiences with 3Ware 6400 3W-6400? Rev. Jeffrey Paul
2003-06-26 21:01 ` Joshua Baker-LePain
2003-06-27 14:36 ` Mike Dresser
2003-06-28 14:00 ` 3ware 7500 performance, was: " Alex Verbitsky
2003-06-28 13:42 ` Mikael Abrahamsson
2003-06-28 15:00 ` Mike Dresser
2003-06-28 15:48 ` Re[2]: " Alex Verbitsky
2003-06-28 14:57 ` Mike Dresser
2003-06-26 22:17 ` David Rees
[not found] ` <2660.208.48.139.163.1056665831.squirrel@www.greenhydrant.c om>
2003-06-26 23:47 ` Maurice Hilarius
2003-06-27 7:06 ` David Rees
2003-06-27 13:24 ` Rev. Jeffrey Paul [this message]
2003-06-27 13:43 ` Gordon Henderson
2003-06-27 15:39 ` Lars Marowsky-Bree
[not found] ` <5.1.1.6.2.20030627094920.03e33780@mail.harddata.com>
[not found] ` <20030627155324.GS7800@marowsky-bree.de>
2003-06-27 16:12 ` Maurice Hilarius
2003-06-27 18:23 ` David Rees
2003-06-27 19:45 ` Rev. Jeffrey Paul
2003-06-28 11:40 ` Re[2]: " Alex Verbitsky
2003-06-27 20:19 ` Gordon Henderson
2003-06-27 18:21 ` David Rees
2003-06-27 10:13 ` Corey McGuire
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=Pine.LNX.4.55.0306270920010.6883@datavibe.net \
--to=sneak@datavibe.net \
--cc=dbr@greenhydrant.com \
--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).