All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: "C. Morgan Hamill" <chamill@wesleyan.edu>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: Question regarding XFS on LVM over hardware RAID.
Date: Wed, 26 Feb 2014 11:49:33 -0600	[thread overview]
Message-ID: <530E292D.2080709@hardwarefreak.com> (raw)
In-Reply-To: <1393423550-sup-1535@al.wesleyan.edu>

On 2/26/2014 8:19 AM, C. Morgan Hamill wrote:
> Excerpts from Stan Hoeppner's message of 2014-02-25 15:08:44 -0500:
>> Only enough to recommend you to replace it immediately with an LSI or
>> Adaptec.  Areca is an absolutely tiny Taiwanese company with inferior
>> product and, from what I gather, horrible support for North American
>> customers, and Linux customers in general.  The vast majority of their
>> customers seem to be SOHOs and individuals using the boards in MS
>> Windows servers, with very few running more than a handful of drives,
>> and few running lots of drives doing serious work.
> 
> Noted.
> 
>> If you run into any kind of performance issue with their board, and
>> explain to them your number of drives and arrays, OS platform and
>> workload, they'll be baffled like a 3rd grader and have no idea how to
>> respond.
> 
> For better or worse, this will be in line with the "support" I've
> experienced from the vast majority of vendors I've had to deal with.

Edu's often have tight(er) budgets so this often goes with the
territory, unfortunately.  On the bright side, one tends to learn quite
a bit about the hardware industry, the secret sauce that separates two
vendors using the same ASICs, where the value add comes from, etc.
This, out of necessity.

>> The Areca uses inferior older technology, has inferior performance,
>> limited firmware feature set which doesn't support spans
>> (concatenation), near non-existent US support especially for advanced
>> Linux workloads/users, only offers battery cache backup, and is all of ...
>>
>> $10 USD cheaper than the category equivalent yet vastly superior LSI.
> 
> Does seem to be the case.
> 
>> By some off chance you don't already know, LSI is the industry gold
>> standard RAID HBA.  They are the sole RAID HBA OEM board supplier to
>> Dell, IBM, Intel, Lenovo, Fujitsu/Siemens, etc, and their ASICs are used
>> by many others on their in house designs.  LSI's ASICs and firmware have
>> seen more Linux workloads of all shapes and sizes than all other
>> vendors' RAID HBAs combined.
> 
> I am aware; all our servers have LSI in them for boot arrays and
> whatnot.
> 
>> Given all of the above, and that there are at least 3 other LSI boards
>> of superior performance, in the same price range for the past year, why
>> did you go with Areca?
> 
> For better or worse, they're what we were able to get from our white box
> vendor.  It will, unfortunately, have to do for now.  I'll be sure to
> make a note for future expansion.

In that case, exercise it mercilessly with your workload to surface any
problems the firmware may have with the triple RAID6 setup.  Yank a
drive from each array while under full IO load, etc.  Even if Areca
can't provide answers or fixes to problems you uncover, if you can
identify problem spots before production, you can document these and
take steps to mitigate them.

> Until then, we'll just have to tread carefully.

>From what I understand their hardware QC is decent so board failure
shouldn't be an issue.  The issues usually deal with firmware
immaturity.  They're a tiny company with limited resources thus they
simply can't do much workload testing with multiple array
configurations.  Thus their customers running higher end workloads often
end up being guinea pigs and identifying firmware deficiencies for them,
and suffering performance chasms in the process.

LSI, Adaptec, etc do have firmware issues as well on occasion.  But
their test lab resources allow them to flesh most of these out before
the boards reach customers.

> Thanks again for all of your help.

You bet.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-26 17:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 14:26 Question regarding XFS on LVM over hardware RAID C. Morgan Hamill
2014-01-29 15:07 ` Eric Sandeen
2014-01-29 19:11   ` C. Morgan Hamill
2014-01-29 23:55     ` Stan Hoeppner
2014-01-30 14:28       ` C. Morgan Hamill
2014-01-30 20:28         ` Dave Chinner
2014-01-31  5:58           ` Stan Hoeppner
2014-01-31 21:14             ` C. Morgan Hamill
2014-02-01 21:06               ` Stan Hoeppner
2014-02-02 21:21                 ` Dave Chinner
2014-02-03 16:12                   ` C. Morgan Hamill
2014-02-03 21:41                     ` Dave Chinner
2014-02-04  8:00                       ` Stan Hoeppner
2014-02-18 19:44                         ` C. Morgan Hamill
2014-02-18 23:07                           ` Stan Hoeppner
2014-02-20 18:31                             ` C. Morgan Hamill
2014-02-21  3:33                               ` Stan Hoeppner
2014-02-21  8:57                                 ` Emmanuel Florac
2014-02-22  2:21                                   ` Stan Hoeppner
2014-02-25 17:04                                     ` C. Morgan Hamill
2014-02-25 17:17                                       ` Emmanuel Florac
2014-02-25 20:08                                       ` Stan Hoeppner
2014-02-26 14:19                                         ` C. Morgan Hamill
2014-02-26 17:49                                           ` Stan Hoeppner [this message]
2014-02-21 19:17                                 ` C. Morgan Hamill
2014-02-03 16:07                 ` C. Morgan Hamill
2014-01-29 22:40   ` Stan Hoeppner

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=530E292D.2080709@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=chamill@wesleyan.edu \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.