linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Zajkowski <jamesez@umich.edu>
To: linux-kernel@vger.kernel.org
Subject: Sparse LUN scanning - 2.4.x
Date: Tue, 11 Jan 2005 14:05:53 -0500	[thread overview]
Message-ID: <cs182h$6nl$1@sea.gmane.org> (raw)

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?

Thanks in advance,

--Jim

-- 
Jim Zajkowski          OpenPGP 0x21135C3    http://www.jimz.net/pgp.asc
System Administrator  8A9E 1DDF 944D 83C3 AEAB  8F74 8697 A823 2113 5C53
UM Life Sciences Institute

 



             reply	other threads:[~2005-01-11 19:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 19:05 Jim Zajkowski [this message]
2005-01-12  0:07 ` Sparse LUN scanning - 2.4.x Michael Clark
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='cs182h$6nl$1@sea.gmane.org' \
    --to=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;
as well as URLs for NNTP newsgroup(s).