From: James Bottomley <James.Bottomley@steeleye.com>
To: "Philip R. Auld" <pauld@egenera.com>
Cc: "Smart, James" <James.Smart@Emulex.com>,
'Patrick Mansfield' <patmans@us.ibm.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: 29 Jan 2004 10:05:45 -0500 [thread overview]
Message-ID: <1075388747.2381.36.camel@mulgrave> (raw)
In-Reply-To: <20040129094910.F11527@vienna.EGENERA.COM>
On Thu, 2004-01-29 at 09:49, Philip R. Auld wrote:
> It needs to be known to the pathing layer if you've got load balancing.
> It has to know which path has the reservation and only use that one.
Well, yes, but your multiple active path implementation just collapsed
back down to single path in the face of reservations, so it would
probably be better simply to use failover in the face of reservations
and clustering.
For the single path case, something like the HP MSA/EVA arrays simply
throw away reservations on path switch over. This allows the user level
watchdog code to reassert them in a cluster down the new path. However,
there are array that will do a path switchover and then return
reservation conflict to everyone (including the taking node). These
arrays will need some type of special handling.
James
next prev parent reply other threads:[~2004-01-29 15:05 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
2004-01-29 14:49 ` Philip R. Auld
2004-01-29 15:05 ` James Bottomley [this message]
-- 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=1075388747.2381.36.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