linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Simon McNair <simonmcnair@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	ayan@marvell.com, andy yan <andyysj@gmail.com>,
	"linux-raid" <linux-raid@vger.kernel.org>
Subject: Re: mvsas with 3.1
Date: Wed, 1 Feb 2012 07:03:09 -0700	[thread overview]
Message-ID: <201202010703.09833.thomas@fjellstrom.ca> (raw)
In-Reply-To: <CAKaSfQDyU1a641ZMBNNJJABhXBQxhPGH=E6sNoss=2JyYgFusw@mail.gmail.com>

On Wed Feb 1, 2012, Simon McNair wrote:
> Hi Thomas,
> I've been trying to get an answer to this same question (I have a
> supermicro AOC-SASLP-MV8 too).  See my post at
> https://lkml.org/lkml/2012/1/30/107  .
> 
> My only suggestion is to get a kernel that's pre 2.6.30 (my Thecus
> 5200 marvell based unit is on 2.6.13 and it seems okay).  If the data
> is mission critical I certainly wouldn't be using the latest kernels
> in production until it had 6+months in a stress test environment (of
> course I'm an obsessive apt-get upgrade which makes me a hypocrite
> 
> :-P).
> 
> I can see from searching lkml.org  for mvsas that there is a lot of
> code going in to this driver and unless your're a linux guru and can
> fix these problems I can only suggest you keep anything important on a
> =< 2.6.13 kernel and monitor the situation.
> 
> Oh, and keep back ups ;-) (again here's me being the hypocrite).
> 
> That's my plan :-(

The older drivers were even worse, they'd have these really nasty pauses, or 
just outright OOPS the entire machine.

That said, I've finally had it with the lack of support. It's been over two 
years since I got the card, and enough is enough. I picked up a refurb IBM 
ServeRaid M1015 (aka: LSI 9220-8i) card. It arrived yesterday. Just have to 
wait and see why grub doesn't like it.

> Simon
> 
> On 13 January 2012 18:44, Thomas Fjellstrom <thomas@fjellstrom.ca> wrote:
> > Is there chance this driver will ever be stable? After more than two
> > years I'm starting to get extremely frustrated. I don't really have the
> > option at the moment to get a new card, otherwise I would, likely a non
> > marvell based device.
> > 
> > It actually managed to last 10 days this time though. Which is a record.
> > The interesting thing is there are no warnings or errors in dmesg coming
> > from the mvsas driver or scsi code. All that's happened is processes
> > lock up when trying to write. Reading seems to be fine.
> > 
> > Just to refresh everyone's memory, it's a AOC-SASLP-MV8 card, has a
> > MV64460/64461/64462 chipset. And I have 7 (seagate 7200.12 SATA drives
> > hooked up).
> > 
> > --
> > Thomas Fjellstrom
> > thomas@fjellstrom.ca
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Thomas Fjellstrom
thomas@fjellstrom.ca

  reply	other threads:[~2012-02-01 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 18:44 mvsas with 3.1 Thomas Fjellstrom
2012-01-17  3:00 ` mvsas with 3.1 (mdraid+xfs locked up, single drive w/xfs not locked up) Thomas Fjellstrom
2012-01-17  3:55   ` Brad Campbell
2012-02-01  9:01 ` mvsas with 3.1 Simon McNair
2012-02-01 14:03   ` Thomas Fjellstrom [this message]
2012-02-01 14:38     ` GRUB doesn't like ServeRAID M1015/LSI 9220-8i (was Re: mvsas with 3.1) John Robinson
2012-02-01 14:42       ` Thomas Fjellstrom
2012-02-01 15:16         ` Hannes Reinecke
2012-02-01 15:22           ` Thomas Fjellstrom
2012-02-01 15:27           ` John Robinson
2012-02-02  3:02         ` Brad Campbell
2012-02-02  4:04           ` Thomas Fjellstrom
2012-02-26 12:57       ` Solved (for me at least!) GRUB doesn't like ServeRAID M1015/LSI 9220-8i John Robinson

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=201202010703.09833.thomas@fjellstrom.ca \
    --to=thomas@fjellstrom.ca \
    --cc=andyysj@gmail.com \
    --cc=ayan@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=simonmcnair@gmail.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;
as well as URLs for NNTP newsgroup(s).