public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Philip R. Auld" <pauld@egenera.com>
To: James Bottomley <James.Bottomley@steeleye.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: Thu, 29 Jan 2004 09:49:10 -0500	[thread overview]
Message-ID: <20040129094910.F11527@vienna.EGENERA.COM> (raw)
In-Reply-To: <1075328212.2534.14.camel@mulgrave>; from James.Bottomley@steeleye.com on Wed, Jan 28, 2004 at 05:16:51PM -0500

Rumor has it that on Wed, Jan 28, 2004 at 05:16:51PM -0500 James Bottomley said:
> 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.
> 

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.
 
> I'm open to suggestions on this,  but I think it should be done
> separately as part of a device ownership API.
> 
> James
> 

-- 
Philip R. Auld, Ph.D.  	        	       Egenera, Inc.    
Principal Software Engineer                   165 Forest St.
(508) 858-2628                            Marlboro, MA 01752

  reply	other threads:[~2004-01-29 14:51 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 [this message]
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=20040129094910.F11527@vienna.EGENERA.COM \
    --to=pauld@egenera.com \
    --cc=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=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