From: Bart Van Assche <bvanassche@acm.org>
To: "Bryn M. Reeves" <bmr@redhat.com>
Cc: Hannes Reinecke <hare@suse.de>,
Steffen Maier <maier@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, Chad Dupuis <chad.dupuis@qlogic.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
James Smart <james.smart@emulex.com>,
James Bottomley <jbottomley@parallels.com>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH] scsi_transport_fc: Make 'port_state' writeable
Date: Fri, 15 Mar 2013 14:41:23 +0100 [thread overview]
Message-ID: <51432503.5000703@acm.org> (raw)
In-Reply-To: <514321FD.7090507@redhat.com>
On 03/15/13 14:28, Bryn M. Reeves wrote:
> On 03/15/2013 12:46 PM, Bart Van Assche wrote:
>> The SCSI EH keeps trying until all outstanding request have been
>> finished. Does lpfc_host_reset_handler() invoke scsi_done() for
>
> I don't think so (ends up calling lpfc_sli_cancel_iocbs() via
> lpfc_hba_down_post() after shutting down the mailbox) but I've not seen
> the EH escalate all the way to host reset in most of my testing -
> usually some time after reaching the bus reset remaining IOs timeout and
> the error bubbles up to device-mapper (all the cases I'm looking at are
> devices managed by a dm-multipath target).
>
> The problem is that getting to this stage can take a very long time -
> much longer than most cluster's node eviction timer for e.g. which is
> the source of much of the complaint about this behaviour.
>
>> outstanding requests ? If not, how about modifying
>> lpfc_host_reset_handler() such that it finishes all outstanding requests
>> if the remote port is not reachable ?
>
> I'm not sure how safe that is in this situation - James mentioned in the
> I_T nexus reset thread concerns about frames that could be delayed etc.
> in the fabric if the host unilaterally abandons IOs (not sure of the
> details for lpfc at this level).
How about using the value of scsi_cmnd.jiffies_at_alloc to finish only
those SCSI commands in the host reset handler that exceeded a certain
processing time ?
Bart.
next prev parent reply other threads:[~2013-03-15 13:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 15:02 [PATCH] scsi_transport_fc: Make 'port_state' writeable Hannes Reinecke
2013-03-14 18:09 ` Steffen Maier
2013-03-15 11:55 ` Hannes Reinecke
2013-03-15 12:01 ` Bryn M. Reeves
2013-03-15 12:24 ` Bart Van Assche
2013-03-15 12:37 ` Bryn M. Reeves
2013-03-15 12:46 ` Bart Van Assche
2013-03-15 13:28 ` Bryn M. Reeves
2013-03-15 13:41 ` Bart Van Assche [this message]
2013-03-15 18:51 ` Mike Christie
2013-03-15 19:13 ` Bart Van Assche
2013-03-15 21:12 ` Mike Christie
2013-03-18 7:09 ` Hannes Reinecke
2013-04-01 21:06 ` James Smart
2013-04-04 6:26 ` Hannes Reinecke
2013-04-05 15:14 ` James Smart
2013-04-12 14:24 ` Chad Dupuis
2013-03-18 21:54 ` Jeremy Linton
2013-04-01 20:51 ` James Smart
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=51432503.5000703@acm.org \
--to=bvanassche@acm.org \
--cc=andrew.vasquez@qlogic.com \
--cc=bmr@redhat.com \
--cc=chad.dupuis@qlogic.com \
--cc=hare@suse.de \
--cc=james.smart@emulex.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.vnet.ibm.com \
--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.