linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Landman <joe.landman@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: /dev/md2 stopped after changing SAS controller
Date: Sun, 15 May 2011 10:29:11 -0400	[thread overview]
Message-ID: <4DCFE337.7090306@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1105150922510.20305@uplift.swm.pp.se>

On 05/15/2011 03:26 AM, Mikael Abrahamsson wrote:
> On Sat, 14 May 2011, Stan Hoeppner wrote:
>
>>
>> http://www.newegg.com/Product/Product.aspx?Item=N82E16816101358
>> http://www.supermicro.com/manuals/other/AOC-SASLP-MV8.pdf
>>
>> Simple JBOD only HBA, no fakeRAID. Uses a Marvell 88SE6480 chip, 8
>> SAS/SATA ports via two SFF8087. $110 USD. I've heard minor rumblings
>> WRT the mvsas driver though I don't recall specifics. The board itself
>> is good quality, as with most things SuperMicro.
>
> MINOR!??? I've had this card for 1.5 years, it still not usable (as far
> as I can discern) as of 2.6.38. Do NOT buy it. Please stop recommending
> this card for Linux use unless it's to your enemies.

+1 to Mikael

We have a number of these.  They are pretty much useless.  We *do not 
recommend them for any purpose whatsoever*.  We got them to test, and 
they were and are wastes of money.

Again, this is why making sure that the bona fides of those making 
recommendations don't begin and end with a google search ...

>
> Buy a 1068E (3081E) based card, they've been working fine for a long time.
>

+1 on that.  We like the 3081E, and the 9211-8i for these purposes. 
Both work quite well.

Again, ignore these cards, they will absorb your money and your time.



-- 
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics, Inc.
email: landman@scalableinformatics.com
web  : http://scalableinformatics.com
        http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615

  reply	other threads:[~2011-05-15 14:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 20:29 /dev/md2 stopped after changing SAS controller Louis-David Mitterrand
2011-05-13 21:33 ` NeilBrown
2011-05-14  8:21   ` Louis-David Mitterrand
2011-05-14  8:27     ` CoolCold
2011-05-14  8:36       ` Roman Mamedov
2011-05-14  8:41         ` CoolCold
2011-05-14 11:58     ` NeilBrown
2011-05-14 12:06       ` Roman Mamedov
2011-05-14 13:00         ` David Brown
2011-05-14 14:19       ` Louis-David Mitterrand
2011-05-14 15:03 ` Stan Hoeppner
2011-05-14 15:18   ` Louis-David Mitterrand
2011-05-14 18:19     ` Stan Hoeppner
2011-05-14 19:15       ` Louis-David Mitterrand
2011-05-14 23:40         ` Stan Hoeppner
2011-05-15  7:26           ` Mikael Abrahamsson
2011-05-15 14:29             ` Joe Landman [this message]
2011-05-15 14:37               ` Louis-David Mitterrand
2011-05-16  6:12                 ` Stan Hoeppner
2011-05-16  9:27                   ` Leslie Rhorer
2011-05-16  5:01               ` Stan Hoeppner
2011-05-16  4:43             ` 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=4DCFE337.7090306@gmail.com \
    --to=joe.landman@gmail.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).