From: James Bottomley <James.Bottomley@steeleye.com>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: 'Patrick Mansfield' <patmans@us.ibm.com>,
"Philip R. Auld" <pauld@egenera.com>,
Simon Kelley <simon@thekelleys.org.uk>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
dm-devel@sistina.com
Subject: RE: Is there a grand plan for FC failover?
Date: 28 Jan 2004 17:16:51 -0500 [thread overview]
Message-ID: <1075328212.2534.14.camel@mulgrave> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C013B0@xbl.ma.emulex.com>
On Wed, 2004-01-28 at 16:02, Smart, James wrote:
> I'd add one additional issue :
>
> 3) SCSI Reservations
>
> I guess this could be considered a part of (2), but given that reservations
> bring in a host of additional problems, and potentially brings up multi-host
> configs/clusters as well...
The current crop of cluster implementations that use reservations manage
quite well in user space alone. Certainly, though, the presence of
reservations can interfere with failover code and may be considered a
problem that needs to be solved in multi-path...it all depends on how
the multi-path devices react to path switching in the face of
reservations.
I'm open to suggestions on this, but I think it should be done
separately as part of a device ownership API.
James
next prev parent reply other threads:[~2004-01-28 22:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 21:02 Is there a grand plan for FC failover? Smart, James
2004-01-28 22:16 ` James Bottomley [this message]
2004-01-29 14:49 ` Philip R. Auld
2004-01-29 15:05 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 19:37 Smart, James
2004-01-29 18:41 Smart, James
2004-01-29 17:35 Smart, James
2004-01-29 18:31 ` Mike Anderson
2004-01-29 18:31 ` James Bottomley
2004-01-26 14:18 Simon Kelley
2004-01-26 15:37 ` James Bottomley
2004-01-28 15:02 ` Philip R. Auld
2004-01-28 16:57 ` James Bottomley
2004-01-28 18:00 ` Philip R. Auld
2004-01-28 20:47 ` Patrick Mansfield
2004-01-28 22:14 ` James Bottomley
2004-01-29 0:55 ` Patrick Mansfield
2004-01-28 22:37 ` Mike Christie
2004-01-29 15:24 ` Philip R. Auld
2004-01-29 16:00 ` James Bottomley
2004-01-29 23:25 ` Mike 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=1075328212.2534.14.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.com \
--cc=dm-devel@sistina.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=pauld@egenera.com \
--cc=simon@thekelleys.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox