From: James Bottomley <James.Bottomley@SteelEye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: mikem@beardog.cca.cpqcorp.net, Andrew Morton <akpm@osdl.org>,
Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: cciss update [2/2] fixes for Steeleye Lifekeeper
Date: 14 Oct 2004 09:37:32 -0500 [thread overview]
Message-ID: <1097764660.2198.11.camel@mulgrave> (raw)
In-Reply-To: <20041014083900.GB7747@infradead.org>
On Thu, 2004-10-14 at 03:39, Christoph Hellwig wrote:
> No, this is bogus. Never call add_disk on a volume that hasn't been
> configured and full set up. If you need to talk to our driver without
> online volumes add a character device.
I don't think so ... it's a volume you know exists but you can't get
access to (in a shared storage configuration). In SCSI we have two
examples of this now:
1. The case where the device responds to inquiry but errors read
capacity (usually because of a reservation conflict). Here we configure
a totally bogus 1GB volume with 512 byte sectors.
2. The case where the device has an illegal sector size. Here we
configure a zero size volume.
In both cases we expose the device in sd but make it effectively
inaccessible because we want to be able to send ioctls to it but not
allow ordinary read/writes. (Although I'd really like not to configure
a bogus size in case 1.). I don't see how the cciss case is any
different from this.
James
next prev parent reply other threads:[~2004-10-14 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 21:22 cciss update [2/2] fixes for Steeleye Lifekeeper mike.miller
2004-10-14 8:39 ` Christoph Hellwig
2004-10-14 13:48 ` mikem
2004-10-14 14:37 ` James Bottomley [this message]
2004-10-14 18:39 ` Christoph Hellwig
2004-10-15 15:05 ` James Bottomley
2004-10-18 16:35 ` mikem
2004-10-18 19:45 ` James Bottomley
2004-10-20 20:15 ` mikem
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=1097764660.2198.11.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=hch@infradead.org \
--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