From: Doug Ledford <dledford@redhat.com>
To: Arjan Van de Ven <arjanv@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Kurt Garloff <garloff@suse.de>,
Linux SCSI list <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@steeleye.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] 4/6: scsi_allow_ghost_devices
Date: Mon, 19 Apr 2004 08:06:22 -0400 [thread overview]
Message-ID: <1082376382.4635.65.camel@compaq.xsintricity.com> (raw)
In-Reply-To: <1082360042.4691.3.camel@laptop.fenrus.com>
On Mon, 2004-04-19 at 03:34, Arjan van de Ven wrote:
> > I'm very unhappy with that. Could you explain why EMC needs this?
> > And even if we have to work around it I'd rather use the blacklist mechanism
> > for this.
>
> they allow the admin to config the box without a lun 0....
> I 100% agree it's blacklist material.
Actually, the original reason for the patch was the fact that some
external boxes use LUN 0 as a control device that you send commands to
in order to init logical volumes. Without access to the control device
(which previously was always shown as offline), you couldn't set the box
up with any linux tools, you would have to set up the logical volumes
under Windows then boot into linux to see them. Since the LUN 0 device
wasn't really offline, but instead was reported as a disk device with no
attached physical device, this patch was created to allow the linux
kernel to send commands to the control device.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2004-04-19 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 18:59 [PATCH] 4/6: scsi_allow_ghost_devices Kurt Garloff
2004-04-18 19:20 ` Christoph Hellwig
2004-04-18 22:14 ` Kurt Garloff
2004-04-19 7:34 ` Arjan van de Ven
2004-04-19 12:06 ` Doug Ledford [this message]
2004-04-19 12:14 ` Christoph Hellwig
2004-04-19 13:34 ` Matthew Wilcox
2004-04-20 17:34 ` Patrick Mansfield
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=1082376382.4635.65.camel@compaq.xsintricity.com \
--to=dledford@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=garloff@suse.de \
--cc=hch@infradead.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