From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-kernel@vger.kernel.org
Cc: "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: mvsas with 3.1
Date: Fri, 13 Jan 2012 11:44:57 -0700 [thread overview]
Message-ID: <201201131144.58044.thomas@fjellstrom.ca> (raw)
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
next reply other threads:[~2012-01-13 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 18:44 Thomas Fjellstrom [this message]
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
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=201201131144.58044.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 \
/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).