From: Michael Reed <mdr@sgi.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
James Smart <James.Smart@Emulex.Com>
Subject: [PATCH 1/1] lpfc: lpfc no longer discovers lun 255
Date: Fri, 04 Dec 2009 10:04:10 -0600 [thread overview]
Message-ID: <4B1932FA.7080407@sgi.com> (raw)
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@sgi.com>
--- 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.
next reply other threads:[~2009-12-04 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 16:04 Michael Reed [this message]
2009-12-04 17:41 ` [PATCH 1/1] lpfc: lpfc no longer discovers lun 255 James Smart
2009-12-04 17:55 ` Michael Reed
2009-12-04 17:58 ` James Bottomley
2009-12-04 18:43 ` Michael Reed
2009-12-10 13:01 ` Brian King
2009-12-10 15:43 ` James Bottomley
2009-12-10 20:03 ` Ed Lin - PTU
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=4B1932FA.7080407@sgi.com \
--to=mdr@sgi.com \
--cc=James.Smart@Emulex.Com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.