From: mikem <mikem@beardog.cca.cpqcorp.net>
To: Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, axboe@suse.de, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: cciss update [2/2] fixes for Steeleye Lifekeeper
Date: Thu, 14 Oct 2004 08:48:29 -0500 [thread overview]
Message-ID: <20041014134829.GA21960@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20041014083900.GB7747@infradead.org>
On Thu, Oct 14, 2004 at 09:39:00AM +0100, Christoph Hellwig wrote:
> On Wed, Oct 13, 2004 at 04:22:53PM -0500, mike.miller@hp.com wrote:
> > This patch addresses a problem with clustering software and also some of our utilies. We had to modify the modify the open specifically for clustering. This is the same as was done for 2.4. We also have to register the reserved volumes with the OS so when the backup server breaks the reservations he can call BLKRRPART to set the volume to the correct size.
> > We also have to register a controller that may not have any logical volumes configured. This is for the online utils as well as clustering.
> >
> > Patch applies to 2.6.9-rc4. Please apply in order.
> > Please consider this for inclusion.
>
> 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.
>
This is the way we've done it since the 2.2 kernel. We have legacy applications
in the field that expect to open c?d0 as the controller. Creating a character
device would require all these apps to change.
mikem
next prev parent reply other threads:[~2004-10-14 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 21:22 mike.miller
2004-10-14 8:39 ` Christoph Hellwig
2004-10-14 13:48 ` mikem [this message]
2004-10-14 14:37 ` James Bottomley
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=20041014134829.GA21960@beardog.cca.cpqcorp.net \
--to=mikem@beardog.cca.cpqcorp.net \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=hch@infradead.org \
--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
all inboxes | Powered by JetHome®