From: Hannes Reinecke <hare@suse.de>
To: Jeremy Linton <jlinton@tributary.com>
Cc: Michael Christie <michaelc@cs.wisc.edu>,
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: Fri, 15 Feb 2013 08:17:36 +0100 [thread overview]
Message-ID: <511DE110.4040506@suse.de> (raw)
In-Reply-To: <511D4FB5.708@tributary.com>
On 02/14/2013 09:57 PM, Jeremy Linton wrote:
> On 2/13/2013 8:43 PM, Michael Christie wrote:
>> For the case where report supported TMFs is not supported can we just have the
>> LLD return some new return code from the eh callback when it
gets FUNCTION_REJECTED.
>> scsi-ml would then clear the eh_*_ok bit, so at least it would
not be called again..
>
>
> Hmm, that seems like a good idea. The question is, does propagating the flag
> change to all the devices on the I_T make sense?
>
Hmm. Again, I've yet to find a storage array which actually _does_
reject a TMF.
None of mine do, not even the latest and greatest NetApp Ontap
version ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-02-15 7:17 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
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 [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=511DE110.4040506@suse.de \
--to=hare@suse.de \
--cc=Elliott@hp.com \
--cc=jlinton@tributary.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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.