From: Jeremy Linton <jlinton@tributary.com>
Cc: chad.dupuis@qlogic.com, Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH][RFC] scsi_transport_fc: Implement I_T nexus reset
Date: Fri, 7 Dec 2012 15:05:45 -0600 [thread overview]
Message-ID: <50C25A29.9030904@tributary.com> (raw)
In-Reply-To: <alpine.WNT.2.00.1212071451330.6432@N5102REMCQXM4BS.qlogic.org>
On 12/7/2012 1:58 PM, Chad Dupuis wrote:
> Also, are there certain port types we wouldn't want to send this reset to
> such as tape?
AFAIK, for tape it shouldn't cause any more harm than the target reset which
happens immediately before it. This patch is infinitely better than the
previous "bus" reset behavior.
That said, its far from perfect. The code (as I understand it) isn't
differentiating between isolating the failure, or bringing out the big
hammer in an attempt to correct problems on a specific I_T_L. If you
drop/reset the I_T because one of the LUN's is misbehaving before verifying
the status of other LUN's on the target, you risk interrupting operations to
functional devices.
next prev parent reply other threads:[~2012-12-07 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 14:51 [PATCH][RFC] scsi_transport_fc: Implement I_T nexus reset Hannes Reinecke
2012-12-07 18:58 ` Mike Christie
2012-12-07 19:58 ` Chad Dupuis
2012-12-07 21:05 ` Jeremy Linton [this message]
2012-12-07 21:20 ` Mike Christie
2012-12-07 22:33 ` Jeremy Linton
2012-12-10 10:18 ` Hannes Reinecke
2012-12-09 15:40 ` Hannes Reinecke
2012-12-09 23:19 ` Mike Christie
2012-12-09 23:31 ` Mike Christie
2012-12-10 2:27 ` Michael Christie
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=50C25A29.9030904@tributary.com \
--to=jlinton@tributary.com \
--cc=chad.dupuis@qlogic.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 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.