public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Arjan Van de Ven <arjanv@redhat.com>,
	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 13:14:10 +0100	[thread overview]
Message-ID: <20040419131410.A10772@infradead.org> (raw)
In-Reply-To: <1082376382.4635.65.camel@compaq.xsintricity.com>; from dledford@redhat.com on Mon, Apr 19, 2004 at 08:06:22AM -0400

On Mon, Apr 19, 2004 at 08:06:22AM -0400, Doug Ledford wrote:
> 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.

Man is that a horrible cludge.  Can't one of the EMC folks on this list
kick their firmware group to fix this horrible crap? I.e. make lun a non-disk
device that can be accessed by sg and isn't marked offline?  It can't be
_that_ difficult.  And btw, what tools actually need that access, does some
have pointers to a tarball - I really wonder what they do.

Yeah, Enterprise storage.  I wonder why people trust EMC to even design
a loo cover.


  reply	other threads:[~2004-04-19 12:14 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
2004-04-19 12:14       ` Christoph Hellwig [this message]
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=20040419131410.A10772@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=dledford@redhat.com \
    --cc=garloff@suse.de \
    --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