From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>
Cc: 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 13:24:47 +0100 [thread overview]
Message-ID: <5143130F.4090702@acm.org> (raw)
In-Reply-To: <51430C4A.7090308@suse.de>
On 03/15/13 12:55, Hannes Reinecke wrote:
> And the LLDD is forced into error recovery which'll take _ages_ as each
> and every command send during error recovery will time out.
Hello Hannes,
I'm analyzing a related but not identical issue with SRP. It would help
if you could tell with which LLDD you ran into this issue and with which
values of fast_io_fail_tmo and dev_loss_tmo.
Bart.
next prev parent reply other threads:[~2013-03-15 12:24 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 [this message]
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
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=5143130F.4090702@acm.org \
--to=bvanassche@acm.org \
--cc=andrew.vasquez@qlogic.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.