public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Roets, Chris" <Chris.Roets@compaq.com>
Cc: "'James Bottomley'" <James.Bottomley@steeleye.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux Cluster using shared scsi
Date: Tue, 01 May 2001 10:45:00 -0400	[thread overview]
Message-ID: <200105011445.KAA01117@localhost.localdomain> (raw)
In-Reply-To: Message from "Roets, Chris" <Chris.Roets@compaq.com>  of "Tue, 01 May 2001 14:07:11 BST." <6B180991CB19D31183E40000F86AF80E037EBD0E@broexc2.bro.dec.com>

Chris.Roets@compaq.com said:
> So, will Linux ever support the scsi reservation mechanism as standard? 

That's not within my gift.  I can merely write the code that corrects the 
behaviour.  I can't force anyone else to accept it.

Chris.Roets@compaq.com said:
> Isn't there a standard that says if you scsi reserve a disk, no one
> else should be able to access this disk, or is this a "steeleye/
> Compaq" standard. 

Use of reservations is laid out in the SCSI-2 and SCSI-3 standards (which can 
be downloaded from the T10 site www.t10.org) which are international in scope. 
 I think the implementation issues come because the reservations part is 
really only relevant to a multi-initiator clustered environment which isn't an 
every day configuration for most Linux users.  Obviously, as Linux moves into 
the SAN arena this type of configuration will become a lot more common, at 
which time the various problems associated with multiple initiators should 
rise in prominence.

James



  reply	other threads:[~2001-05-01 14:46 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 [this message]
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
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=200105011445.KAA01117@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=Chris.Roets@compaq.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox