From: James Bottomley <James.Bottomley@SteelEye.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Doug Ledford <dledford@redhat.com>,
Mike Anderson <mike.anderson@us.ibm.com>,
Eric.Ayers@intec-telecom-systems.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: Thu, 03 May 2001 09:52:03 -0400 [thread overview]
Message-ID: <200105031352.JAA01246@localhost.localdomain> (raw)
In-Reply-To: Message from James Bottomley <James.Bottomley@SteelEye.com> of "Thu, 03 May 2001 08:53:42 EDT." <200105031253.IAA00988@localhost.localdomain>
There is another nasty in multi-port arrays that I should perhaps point out:
a bus reset isn't supposed to drop the reservation if it was taken on another
port. A device or LUN reset will drop reservations on all ports. This
behaviour, although clearly mandated by the SCSI-3-SPC, is rather patchily
implemented in arrays and I have seen some multi-port arrays that will,
illegally, drop reservations on all ports on receipt of a bus reset.
Unfortunately, most Linux SCSI drivers won't issue device resets on command,
they'll only issue bus resets, so it is possible to get into a situation where
you cannot break a reservation belonging to a dead machine, if you set up a
point-to-point cluster rather than a true shared-scsi one.
James
next prev parent reply other threads:[~2001-05-03 13:52 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
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 [this message]
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=200105031352.JAA01246@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=Chris.Roets@compaq.com \
--cc=Eric.Ayers@intec-telecom-systems.com \
--cc=dledford@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.