All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Richard Scobie <richard@sauce.co.nz>, linux-scsi@vger.kernel.org
Subject: Re: mptsas problem
Date: Sun, 13 Apr 2008 13:06:44 -0400	[thread overview]
Message-ID: <20080413170644.GA1234@animx.eu.org> (raw)
In-Reply-To: <1208105925.4707.27.camel@localhost.localdomain>

James Bottomley wrote:
> On Sun, 2008-04-13 at 12:48 -0400, Wakko Warner wrote:
> > > Actually, I'd say this is a signal for NCQ errors with the drive.
> > 
> > Unless it's this specific drive firmware, I'd have to disagree.  I have 6 of
> > the exact same drives (can't confirm firmware is the same though) in raid5
> > on an aic9410 sas controller w/o problems.  The queue_depth for those are
> > 31.  I considered setting that value to the ones I'm having problems with,
> > but I really don't want to go through another 4 hour rebuild.
> 
> Well, yes, different revs of the firmware can behave differently.  The
> libata-core blacklist includes the firmware version as part of the
> pattern matching.

> There's an easy way to verify:  smartctl -i will print the firmware
> version string.

The aic sas one shows 3.AAE
The lsi mptsas can't be queried:
# smartctl -d scsi -i /dev/sdc
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Serial number:             3QD076X8
Device type: disk
Local Time is: Sun Apr 13 13:02:36 2008 EDT
Device supports SMART and is Enabled
Temperature Warning Disabled or Not Supported
#

I tried -d ata, -d sat and not using -d, provided no information.  -T
permissive didn't work either.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???

  reply	other threads:[~2008-04-13 17:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 23:40 mptsas problem Richard Scobie
2008-04-07  1:04 ` Wakko Warner
2008-04-13 13:00   ` Douglas Gilbert
2008-04-13 14:39     ` James Bottomley
2008-04-13 14:31   ` James Bottomley
2008-04-13 16:48     ` Wakko Warner
2008-04-13 16:58       ` James Bottomley
2008-04-13 17:06         ` Wakko Warner [this message]
2008-04-13 17:37           ` James Bottomley
2008-04-13 20:49             ` Wakko Warner
2008-04-14 18:16               ` Moore, Eric
2008-04-14 21:34                 ` Wakko Warner
2008-04-15 17:26                   ` Moore, Eric
2008-04-15 22:49                     ` Wakko Warner
2008-04-13 22:22             ` Douglas Gilbert
2008-04-13 23:51               ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2008-04-06 19:56 Wakko Warner
     [not found] ` <0631C836DBF79F42B5A60C8C8D4E8229F64FC1@NAMAIL2.ad.lsil.com>
2008-04-07  1:07   ` Wakko Warner
2008-04-07 11:36     ` Bernd Schubert
2008-04-07 15:16     ` Moore, Eric
2008-04-07 16:54       ` Wakko Warner

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=20080413170644.GA1234@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=richard@sauce.co.nz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.