From: Michael Clark <michael@metaparadigm.com>
To: Jim Zajkowski <jamesez@umich.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sparse LUN scanning - 2.4.x
Date: Wed, 12 Jan 2005 08:07:53 +0800 [thread overview]
Message-ID: <41E46A59.2010205@metaparadigm.com> (raw)
In-Reply-To: <cs182h$6nl$1@sea.gmane.org>
Jim Zajkowski wrote:
> Hi there,
>
> We have an Apple Xserve RAID, connected through a FC switch. The RAID
> has LUN-masking enabled, such that one of our Linux boxes only gets
> LUN 1 and not LUN 0. We're running the 2.4.x kernel series now, since
> this is under a RHEL envinronment.
>
> The problem is this: since LUN 0 does not show up -- specifically, it
> can't read the vendor or model informaton -- the kernel SCSI scan does
> not match with the table to tell the kernel to do sparse LUN
> scanning... so the RAID does not appear.
>
> I can make the RAID show up by injecting a add-single-device to the
> SCSI proc layer. Trivially patching scsi_scan.c to always do sparse
> scanning works as well. No hokery with max_scsi_luns or ghost devices
> works.
>
> I'm considering making a patch to add a kernel option to force sparse
> scanning. Is there a better way?
>
Add the Xserve with the BLIST_SPARSELUN flag into the blacklist/quirks
table in drivers/scsi/scsi_scan.c
~mc
next prev parent reply other threads:[~2005-01-12 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 19:05 Sparse LUN scanning - 2.4.x Jim Zajkowski
2005-01-12 0:07 ` Michael Clark [this message]
2005-01-12 2:11 ` Jim Zajkowski
2005-01-12 9:50 ` Michael Clark
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=41E46A59.2010205@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=jamesez@umich.edu \
--cc=linux-kernel@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