From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-raid@vger.kernel.org
Subject: Re: /dev/md2 stopped after changing SAS controller
Date: Sat, 14 May 2011 13:19:44 -0500 [thread overview]
Message-ID: <4DCEC7C0.80306@hardwarefreak.com> (raw)
In-Reply-To: <20110514151812.GA3074@apartia.fr>
On 5/14/2011 10:18 AM, Louis-David Mitterrand wrote:
> On Sat, May 14, 2011 at 10:03:44AM -0500, Stan Hoeppner wrote:
>> On 5/13/2011 3:29 PM, Louis-David Mitterrand wrote:
>>
>>> I've been having very bad performance with an LSISAS2008 controller
>>> attached to 8 WD Caviar Black 1TB disks.
>>
>> What is the nature of this 'very bad performance'? Did you recently
>> upgrade kernel/driver and run into a regression? If not, either the HBA
>> has developed a circuit defect, or the problem lies elsewhere, either a
>> backplane/cabling issue, or a drive going south.
>
> The performance problem can be clearly attributed to that model of the
> LSI card because with the Adaptec card and the same cables and disks the
> problem disappears.
How have you ascertained this already? As of 2 hours ago you still
don't have your filesystem(s) back up and running after the HBA swap. I
would assume a backup restore of a few TB would take more than a few
hours...
> The LSI card has always performed very poorly with all kernel versions I
> tried, including the very latest, and the with most recent firmware
> revisions from LSI.
LSI HBAs are usually held in pretty high regard. Which specific part#
are we talking about? Is this an OEM Dell HBA?
> After bricking the card while trying to change its firmware to an "IT"
> version (Initiatior Target i.e. non-raid) I had Dell send me a new one
> on warranty and the performance problem remained.
You still haven't described the nature of the performance problem. This
is a technical mailing list after all.
>> Do you have any log entries showing problems with the LSI HBA? Drive
>> errors? What does smartctl tell you about each drive?
>
> No error. Just plain sloth.
Interesting technical description. Now we have yet another post in the
Interwebs archives stating a certain piece of hardware is junk without
any real explanation as to the nature of the problem...
--
Stan
next prev parent reply other threads:[~2011-05-14 18:19 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 [this message]
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
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=4DCEC7C0.80306@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@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).