lkml.org 
[lkml]   [2005]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Sparse LUN scanning - 2.4.x
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.046 / U:7.876 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site