public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Mike Anderson <mike.anderson@us.ibm.com>
Cc: Eric.Ayers@intec-telecom-systems.com,
	James Bottomley <James.Bottomley@steeleye.com>,
	"Roets, Chris" <Chris.Roets@compaq.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux Cluster using shared scsi
Date: Wed, 02 May 2001 13:50:50 -0400	[thread overview]
Message-ID: <3AF048FA.1B5EA399@redhat.com> (raw)
In-Reply-To: LINKIFYdBceGaCHcJFaADIDAcHBbbIfBCdEeBeJIFIAJGGGLINKIFYJaBBbEGacBeDfHdCJIecBfdJabIAFHABCICaGbFC <15086.60620.745722.345084@gargle.gargle.HOWL> <3AF025AE.511064F3@redhat.com> <20010502102037.A19349@us.ibm.com>

Mike Anderson wrote:
> 
> Doug,
> 
> A question on clarification.
> 
> Is the configuration you are testing have both FC adapters going to the same
> port of the storage device (mutli-path) or to different ports of the storage
> device (mulit-port)?
> 
> The reason I ask is that I thought if you are using SCSI-2 reserves that the
> reserve was on a per initiator basis. How does one know which path has the
> reserve?

Reservations are global in nature in that a reservation with a device will
block access to that device from all other initiators, including across
different ports on multiport devices (or else they are broken and need a
firmware update).

> On a side note. I thought the GFS project had up leveled there locking / fencing
> into a API called a locking harness to support different kinds of fencing
> methods. Any thoughts if this capability could be plugged into this service so
> that users could reduce recoding depending on which fencing support they
> selected.

I wouldn't know about that.

-- 

 Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
      Please check my web site for aic7xxx updates/answers before
                      e-mailing me about problems

  reply	other threads:[~2001-05-02 17:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01 13:07 Linux Cluster using shared scsi Roets, Chris
2001-05-01 14:45 ` James Bottomley
2001-05-01 16:10   ` Doug Ledford
2001-05-01 17:05     ` Eric Z. Ayers
2001-05-01 20:38       ` Alan Cox
2001-05-01 20:52         ` James Bottomley
2001-05-01 21:07         ` Eric Z. Ayers
2001-05-01 21:24           ` Alan Cox
2001-05-02 15:20       ` Doug Ledford
2001-05-02 16:37         ` Eddie Williams
2001-05-02 17:20         ` Mike Anderson
2001-05-02 17:50           ` Doug Ledford [this message]
2001-05-02 18:55             ` Mike Anderson
2001-05-02 20:31               ` Doug Ledford
2001-05-03 12:53                 ` James Bottomley
2001-05-03 13:52                   ` James Bottomley
2001-05-02 17:39         ` Max TenEyck Woodbury
2001-05-02 17:47           ` Doug Ledford
2001-05-02 21:03             ` Pavel Machek
2001-05-03 19:57               ` Eric Z. Ayers
2001-05-03 22:32                 ` Jonathan Lundell
2001-05-02 21:47             ` Max TenEyck Woodbury
2001-05-02 23:16               ` Doug Ledford
2001-05-04 14:52             ` Eddie Williams
  -- strict thread matches above, loose matches on Subject: below --
2001-04-27 15:11 James Bottomley
2001-04-27 13:18 Roets, Chris

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=3AF048FA.1B5EA399@redhat.com \
    --to=dledford@redhat.com \
    --cc=Chris.Roets@compaq.com \
    --cc=Eric.Ayers@intec-telecom-systems.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.anderson@us.ibm.com \
    /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