Bug 167965
Summary: | Fusion MPT SCSI driver LSI 22320-R | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Brad Isbell <bisbell> |
Component: | kernel | Assignee: | Tom Coughlan <coughlan> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | petrides |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 18:54:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brad Isbell
2005-09-09 21:19:59 UTC
Have further tested RHEL U4 and have not been able to find a workable solution. It has the same problem that update 3 did- can only see LUN 0. RHEL 3 will only scan past LUN 0 if you set the max_scsi_luns parameter. To do this you must add the line "options scsi_mod max_scsi_luns=256" to /etc/modules.conf, re-make the initrd, and reboot. After you do this, RHEL 3 probes the LUN space sequentially starting with LUN 0. It stops when it finds a gap. The way to get it to scan past a gap is to add the device to scsi_scan.c. I do not see the Sun StorEdge 3310 listed there, but I do see these, for example: {"SUN", "StorEdge 3510 ", "*", BLIST_SPARSELUN}, {"SUN", "StorEdge 3511 ", "*", BLIST_SPARSELUN}, Are your LUNs numberred sequentially starting with LUN 0? RHEL 4 uses the Report LUNs command, so it usually does not have these problems if the device supports that SCSI command. Does the storage device support the Report LUNs command? Please post the messages in /var/log/messages that show up when you try to configure this device. Thank you very much. Reverting to NEEDINFO. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |