linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason White <jason@jasonjgw.net>
To: linux-scsi@vger.kernel.org
Subject: Re: SCSI queue warnings under 2.6.31 with LSI SAS1064E controller
Date: Fri, 9 Oct 2009 22:51:30 +0000 (UTC)	[thread overview]
Message-ID: <haoepi$2s4$1@ger.gmane.org> (raw)
In-Reply-To: 0D1E8821739E724A86F4D16902CE275C1C8ED6A4B4@inbmail01.lsi.com

Desai, Kashyap <Kashyap.Desai@lsi.com> wrote:

>Now coming to the real issue.
>I am suspecting there may be IO errors with your drive coming very frequently.
>
>QUEUE FULL event is coming from Firmware whenever any change happens in
>device queue depth. This will only happens in IO error path. (We can
>think of flow control will kicked off when IO error occurs at firmware
>level and they will inform Driver saying Queue full event).
>
>In other words,
>If you replace with newer SAS drive, things may work fine even with 2.6.31.
>
>As you have mentioned that this SAS drive was previously used for
>striping, there may be possibility of poor performance of your SAS
>drive.

Thanks for the explanation. Is there a safe way to obtain IO error data from the
drives under Linux?

Since they are configured for striping, the two drives appear as a single SCSI
device /dev/sda
The drives are both SEAGATE  ST373454SS



      reply	other threads:[~2009-10-09 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  3:07 SCSI queue warnings under 2.6.31 with LSI SAS1064E controller Jason White
2009-10-09 12:04 ` Desai, Kashyap
2009-10-09 22:51   ` Jason White [this message]

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='haoepi$2s4$1@ger.gmane.org' \
    --to=jason@jasonjgw.net \
    --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).