Thanks Mike. Wonder if that change broke other drivers too...
Acked-By: James Smart <james.smart@xxxxxxxxxx>
-- james s
Michael Reed wrote:
A change in lun scanning range in scsi_scan.c ( ">" becomes ">=") results
in lpfc no longer discovering lun 255 of my test configuration. This
patch adjusts lpfc_attr.c to discover lun 255 again.
scsi: host 3 channel 0 id 17 lun255 has a LUN larger than allowed by the host adapter
Signed-off-by: Michael Reed <mdr@xxxxxxx>
--- scsi-misc-2.6/drivers/scsi/lpfc/lpfc_attr.c 2009-12-01 16:18:40.000000000 -0600
+++ scsi-misc-2.6-modified/drivers/scsi/lpfc/lpfc_attr.c 2009-12-04 10:01:52.091503203 -0600
@@ -3099,10 +3099,10 @@ LPFC_VPORT_ATTR(discovery_threads, 32, 1
/*
# lpfc_max_luns: maximum allowed LUN.
-# Value range is [0,65535]. Default value is 255.
+# Value range is [0,65535]. Default value is 256, 1 greater than max lun number.
# NOTE: The SCSI layer might probe all allowed LUN on some old targets.
*/
-LPFC_VPORT_ATTR_R(max_luns, 255, 0, 65535, "Maximum allowed LUN");
+LPFC_VPORT_ATTR_R(max_luns, 256, 0, 65535, "Maximum allowed LUN");
/*
# lpfc_poll_tmo: .Milliseconds driver will wait between polling FCP ring.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
