From: Ewan Milne <emilne@redhat.com>
To: James.Smart@emulex.com
Cc: Hannes Reinecke <hare@suse.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
Chad Dupuis <chad.dupuis@qlogic.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: Error handling on FC devices
Date: Tue, 27 Nov 2012 15:03:21 -0500 [thread overview]
Message-ID: <1354046601.4420.14.camel@localhost.localdomain> (raw)
In-Reply-To: <50B3EDEA.40008@emulex.com>
On Mon, 2012-11-26 at 17:32 -0500, James Smart wrote:
> Given path switching is somewhat separate from the i/o, would it better
> to send a notification of a path-fail condition as part of the eh,
> rather than hinging it on the individual i/o. Yes, the i/o is still in
> limbo and can't be switched to the new path, but other i/o could without
> incurring the delay.
Is there a potential issue with a write that is taking a long time on
one path, which could cause path switching for subsequent writes to
another path, before the disposition of the first write is known?
next prev parent reply other threads:[~2012-11-27 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 12:41 Error handling on FC devices Hannes Reinecke
2012-11-26 22:32 ` James Smart
2012-11-27 20:03 ` Ewan Milne [this message]
2012-11-27 20:29 ` Elliott, Robert (Server Storage)
2012-11-28 7:09 ` Hannes Reinecke
2012-11-29 16:02 ` James Smart
2012-11-30 11:44 ` Hannes Reinecke
2012-11-30 16:54 ` Mike Christie
2012-12-03 7:15 ` Hannes Reinecke
2012-12-03 17:19 ` Jeremy Linton
2012-12-03 22:52 ` Elliott, Robert (Server Storage)
2012-12-04 15:56 ` Kipp Aldrich
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=1354046601.4420.14.camel@localhost.localdomain \
--to=emilne@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=James.Smart@emulex.com \
--cc=andrew.vasquez@qlogic.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.