From: Jeremy Linton <jlinton@tributary.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Linux Scsi <linux-scsi@vger.kernel.org>,
"Elliott, Robert (Server Storage)" <Elliott@hp.com>
Subject: Re: [PATCH] Use a more selective error recovery strategy based on device capabilities
Date: Wed, 13 Feb 2013 09:46:13 -0600 [thread overview]
Message-ID: <511BB545.7060600@tributary.com> (raw)
In-Reply-To: <511B8FBF.9000705@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/13/2013 7:06 AM, Hannes Reinecke wrote:
> But unfortunately it failed the reality check; of my zoo of storage arrays
> only NetApp OnTap 8.X and HP P2000 supports the REPORT SUPPORTED TASK
> MANAGEMENT FUNCTIONS command. None of the others (HP EVA, NetApp E-Series,
> EMC Clariion CX-3) do.
I'm not really surprised. I've had better luck with devices that report
compliance with more recent versions of the specification. Of the those, I
would guess slightly more than 50% support it. That includes tape drives,
changer devices, and raid controllers. Of the ones I've tested that support
it, they almost always report 0xDA for the first byte. Which correspond to
abort task, abort task set, clear task set, lun reset and target reset.
The patch also includes some "reasonable" defaults based on SCSI version,
which I think vastly improves the overall error handling situation. Querying
the device is just the last little icing.
But its a chicken and egg thing, the command is optional, hardly anyone sends
it, so few of the device manufactures have implemented it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRG7VFAAoJEL5i86xrzcy7TjwH/R/V52LW66OPSwWVJHjVcbM/
ZQ7ekWZ48oKy4zQrCjpyKMFXqsH5gsMinoruUhiu/Zt8kmef88jti+aMe1RDyCbp
L2fFc5lUOIpHFkzWXCykq8f9ZDcxIi8cLcCR08S71gTZqo/E0gVqYKEzInXtATCQ
HK9yjX7g3FkzYVl9ASiLeBPUT4/kk7IhN+iagc0S+VY8zBG/+jQC9RykenbnAUU1
YLmWsWmzyWiTshk+vmBBpcikk+EEnB25NXZz6cqDSWGcm/wWq4Mcj9i6KvC9tKSr
PzW+0/T2LtedGCTZKnFgNsn1jMJtjId+soAt5Ho4nZD+BHYcr2iSckzWxX3defs=
=hDMi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-13 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 18:19 [PATCH] Use a more selective error recovery strategy based on device capabilities Jeremy Linton
2013-02-12 20:57 ` Elliott, Robert (Server Storage)
2013-02-12 22:00 ` Jeremy Linton
2013-02-13 13:06 ` Hannes Reinecke
2013-02-13 15:46 ` Jeremy Linton [this message]
2013-02-14 2:43 ` Michael Christie
2013-02-14 20:57 ` Jeremy Linton
2013-02-14 23:42 ` Elliott, Robert (Server Storage)
2013-02-15 15:17 ` Jeremy Linton
2013-02-15 7:17 ` Hannes Reinecke
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=511BB545.7060600@tributary.com \
--to=jlinton@tributary.com \
--cc=Elliott@hp.com \
--cc=hare@suse.de \
--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