Bug 187773
Summary: | MPIO Support for lpfc | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Falko Pilz <falko.pilz> |
Component: | kernel | Assignee: | Tom Coughlan <coughlan> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 16:00:58 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
Falko Pilz
2006-04-03 15:27:22 UTC
The direction that Linux is taking is to make all the lower-level drivers present all paths to a device as separate devices. It is then up to the DM-multipath component to combine the paths into a virtual device. The Qlogic and the Emulex drivers in RHEL 3 and 4 have always done this by default. If your Qlogic driver is combining multiple paths, then I believe you are not using the driver that ships with RHEL, or you are setting some non-default parameter. The output shown above, where you have "unknown device type", "Type: RAID", and sg driver rather than sd driver may be a different problem. Please upgrade to Update 3, make sure that the Emulex HBA has been granted access to the LUNs, and try this again. Post the full /var/log/messages if there is still a problem. Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |