From: Greg Smith <gsmith@gregsmith.com>
To: Jeffrey Baker <jwbaker@gmail.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: 3ware vs Areca
Date: Sun, 20 Jul 2008 19:10:18 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0807160343400.11182@westnet.com> (raw)
In-Reply-To: <fd145f7d0807150854p2c28b182k2ac4928b73c290c8@mail.gmail.com>
References: <581D2333-E731-4843-BC31-39840E272C62@torgo.978.org>
<Pine.GSO.4.64.0807111507040.21818@westnet.com>
<fd145f7d0807111239h5611a0f6r3fd682835d357d73@mail.gmail.com>
<Pine.GSO.4.64.0807150010120.6649@westnet.com>
<fd145f7d0807150746q4cd5b1ebg4ddab2f9a27dfb99@mail.gmail.com>
<Pine.GSO.4.64.0807151116550.4435@westnet.com>
<fd145f7d0807150854p2c28b182k2ac4928b73c290c8@mail.gmail.com>
On Tue, 15 Jul 2008, Jeffrey Baker wrote:
> Debian "etch", which has a 2.6.18 kernel. I have contacted Areca
> support (as well as the linux-scsi mailing list) and their responses
> are usually either 1) upgrade the driver and/or firmware even though I
> have the latest drivers and firmware
Well, technically you don't have the latest driver, because that's the one
that comes with the latest Linux kernel. I'm guessing you have RHEL5 here
from that fact that you're using 2.6.18. I have a CentOS5 system here
with an Areca card in it. It installed it initially with the stock 2.6.18
kernel there but it never worked quite right; all sorts of odd panics
under heavy load. All my problems went away just by moving to a generic
2.6.22, released some time after the Areca card became of more first-class
citizen maintained actively by the kernel developers themselves.
> 2) vague statements about the disk being incompatible with the
> controller.
That sort of situation is unfortunate but I don't feel it's unique to
Areca. There's lots of reasons why some manufacturers end up with drives
that don't work well with some controllers, and it is hard to assign blame
when it happens. There is something to be said for buying more integrated
and tested systems; ultimately if you build stuff from parts, you're kind
of stuck being the QA and that process presumes that you may discover
incompatible combinations and punt them out in place of ones that do.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com, jwbaker@gmail.com
Subject: Re: 3ware vs Areca
In-Reply-To: <Pine.GSO.4.64.0807160343400.11182@westnet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox