From: "Keith Baker" <krbaker@metacarta.com>
To: linux-scsi@vger.kernel.org
Subject: MegaSAS Hang on Smart Query
Date: Thu, 29 Jun 2006 20:29:45 -0400 (EDT) [thread overview]
Message-ID: <3541.10.0.0.113.1151627385.squirrel@webmail.metacarta.com> (raw)
I've been having a hang with 2.6.16.22 and the megasas driver. I'm pretty
sure it has to do with a smartctl -a <logical drive>. The SCSI layer gets
all sorts of in a twist.
megasas: waiting for 2 commands to complete
- repeats a bunch of times then -
sd 0:2:0:0: rejecting I/O to offline device
Given a bit of wisdom in a driver distributed by dell which mentioned the
controller not responding to a cache inqury... isn't the correct thing to
do respond with some sort of unsupported response? not just ignore the
query?
I've hunted around for patches around this problem but haven't found any,
of course "don't use smart against a logical drive" works, but I'm not the
only one using these boxes and it does cause the system to go down.
--
Keith Baker
MetaCarta, Inc
350 Massachusetts Ave, 4th Floor
Cambridge, MA 02139 USA
www.metacarta.com <http://www.metacarta.com>
next reply other threads:[~2006-06-30 0:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 0:29 Keith Baker [this message]
2006-06-30 3:03 ` MegaSAS Hang on Smart Query Douglas Gilbert
2006-06-30 18:49 ` Keith Baker
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=3541.10.0.0.113.1151627385.squirrel@webmail.metacarta.com \
--to=krbaker@metacarta.com \
--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