linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
	Andrew Martin <amartin@xes-inc.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Automatically drop caches after mdadm fails a drive out of an array?
Date: Thu, 13 Feb 2014 22:53:02 -0600	[thread overview]
Message-ID: <52FDA12E.2070502@hardwarefreak.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402131822190.24915@uplift.swm.pp.se>

On 2/13/2014 11:25 AM, Mikael Abrahamsson wrote:
> On Thu, 13 Feb 2014, Andrew Martin wrote:
> 
>> Note that I added a new, replacement drive to the array at 17:09. In
>> lieu of Marvel SAS cards, what would you recommend?
> 
> LSI 2008 is very well tested HBA controller, it exists in many vendors'
> cards. Works properly with 4TB drives (and larger I presume). For
> instance the LSI SAS 9211-8i HBA has this chip.

Agreed, LSI based HBAs are all pretty reliable.  These chips can be
found on motherboards, LSI branded HBAs, as well as IBM, Intel, and
other branded HBAs.  The multi-lane Adaptecs are good as well.

Honestly, I've only really heard of serious problems with the mvsas
driver and the Marvell SAS 88SE64xx based HBAs, most often the
Supermicro, but also the Highpoint 2600 family.  There may be others.

-- 
Stan

  reply	other threads:[~2014-02-14  4:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1413719638.30344.1392138285471.JavaMail.zimbra@xes-inc.com>
2014-02-11 17:11 ` Automatically drop caches after mdadm fails a drive out of an array? Andrew Martin
2014-02-11 19:54   ` NeilBrown
2014-02-11 23:10     ` Andrew Martin
2014-02-12  0:11       ` Stan Hoeppner
2014-02-12 14:44         ` Andrew Martin
2014-02-13  8:29           ` Stan Hoeppner
2014-02-13 14:57             ` Andrew Martin
2014-02-13 17:25               ` Mikael Abrahamsson
2014-02-14  4:53                 ` Stan Hoeppner [this message]
2014-02-14 22:40                   ` Andrew Martin

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=52FDA12E.2070502@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=amartin@xes-inc.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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).