From: Stan Hoeppner <stan@hardwarefreak.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
linux-xfs@oss.sgi.com
Subject: Re: 3.9.0: general protection fault
Date: Thu, 09 May 2013 02:16:34 -0500 [thread overview]
Message-ID: <518B4D52.2090807@hardwarefreak.com> (raw)
In-Reply-To: <20130507220742.GC24635@dastard>
On 5/7/2013 5:07 PM, Dave Chinner wrote:
>> And I just wonder what you are going to do with the information
>> about the hardware. So it is an Areca hw-raid5 device with 9 disks.
>> But does this help? It doesn't tell if one of the disks reads/writes
>> with hickups or provides any performance characteristics at all.
>
> Yes, it does, because Areca cards are by far the most unreliable HW
> RAID you can buy, which is not surprising because they are also the
> cheapest. This is through experience - we see reports of filesystems
> being badly corrupted ever few months because of problems with Areca
> controllers.
And the sad part is that they're not that much lower priced than a
comparable LSI card, at least in N. America. Newegg sells a 28 port LSI
for $1500 and a 28 port Areca for $1300--a paltry 13% difference. Areca
packs 8x more DRAM onto this board--4GB vs 512MB--via a standard DIMM
socket, and touts the larger RAM capacity and expandability as a big
performance booster. AIUI this is only partially true. The larger
capacity for the most part simply helps their weak firmware keep pace
with some workloads, mainly large streaming, but the random IO
performance of the Areca's isn't all that great, and regardless of the
size DIMM once inserts random performance doesn't change much.
Regarding reliability, it's interesting to note that the RAID card
industry as a whole began moving away from standard socketed DRAM quite
some time ago. When a manufacturer solders DRAM chips to the board they
have direct control over memory quality and the testing/verification
process of the finished product. So when the customer installs and uses
the board there are no surprises here. With standard DIMM socketed
boards the customer can insert any DIMM s/he wishes, and there's no
guarantee of the quality/reliability of the DIMM, nor the complete unit.
AFAIK Areca has the only line of RAID cards on the market with a socket
for standard DRAM. HP uses a socket design but the daughterboard holds
more than just DRAM, and you must use HP's daughterboard, thus they
control quality. I wonder how many of the people who have problems with
their Areca board had inserted aftermarket DIMMs, vs those using factory
memory who simply ran into firmware or board QC problems.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-05-09 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 14:45 3.8.7: general protection fault Bernd Schubert
2013-05-06 8:14 ` 3.9.0: " Bernd Schubert
2013-05-06 9:40 ` Bernd Schubert
2013-05-06 12:28 ` Dave Chinner
2013-05-06 12:47 ` Bernd Schubert
2013-05-07 1:12 ` Dave Chinner
2013-05-07 11:18 ` Bernd Schubert
2013-05-07 22:07 ` Dave Chinner
2013-05-08 17:48 ` Bernd Schubert
2013-05-09 0:41 ` Dave Chinner
2013-05-10 10:19 ` Bernd Schubert
2013-05-10 13:33 ` Eric Sandeen
2013-05-11 0:12 ` Dave Chinner
2013-06-03 16:39 ` Bernd Schubert
2013-05-09 7:16 ` Stan Hoeppner [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=518B4D52.2090807@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=david@fromorbit.com \
--cc=linux-xfs@oss.sgi.com \
/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