public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: mikem <mikem@beardog.cca.cpqcorp.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Jens Axboe <axboe@suse.de>
Subject: Re: clustering and 2.6
Date: 07 Sep 2004 12:40:50 -0400	[thread overview]
Message-ID: <1094575251.1716.113.camel@mulgrave> (raw)
In-Reply-To: <20040907161254.GA23325@beardog.cca.cpqcorp.net>

On Tue, 2004-09-07 at 12:12, mikem wrote:
> All,
> I'm having some issues when trying to use some clustering software when
> running any 2.6.x kernel.
> Basically, there are 2 nodes connected to 1 storage storage enclosure.
> When node 1 comes up it reserves the volume(s) in the enclosure. When
> node 2 comes up the read capacity fails as expected because of the 
> SCSI reservation. However, if node 1 fails node 2 breaks the reservation,
> but cannot register the disk. At this time we're assuming it's because the read
> capacity failed and the size of the disk is zero blocks.
> 
> The SCSI mid-layer sets a bogus size on a device when read capacity fails.
> Is this the preferred way to get around this issue? Seems like there
> should be a better way.
> 
> Any input is greatly appreciated.

The bogus size thing is a holdover from the old days.

However, I recently did a test where I forced the size to zero.  What I
see is that the partition does indeed not get registered (even for the
whole disc device).  However I can still send a BLKRRPART ioctl to it
trigger a rescan and get the correct size.

James



      parent reply	other threads:[~2004-09-07 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 16:12 clustering and 2.6 mikem
2004-09-07 16:34 ` Christoph Hellwig
2004-09-07 16:40 ` James Bottomley [this message]

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=1094575251.1716.113.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikem@beardog.cca.cpqcorp.net \
    /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