Bug 158459
Summary: | RHEL 3 configures non-existent SCSI target devices | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Tom Coughlan <coughlan> |
Component: | kernel | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | kanderso, nobody+wcheng, peterm, petrides, sandeen, tburke, tkincaid |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHSA-2005-663 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-28 15:11:24 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: | |||
Bug Depends On: | |||
Bug Blocks: | 156320 |
Description
Tom Coughlan
2005-05-22 15:43:38 UTC
A fix for this problem has just been committed to the RHEL3 U6 patch pool this evening (in kernel version 2.4.21-32.7.EL). I did a test to confirm this fix. I used Emulex attached to Clariion. Saw the problem on 2.4.21-32.ELsmp. Saw it was fixed on 2.4.21-32.8.ELsmp. FWIW, we saw a related problem, with the same fix. Wish I'd found this bug before I debugged it independently :) In our case, we have a raid in RDAC mode, where luns 1-3 belong to one controller, and luns 4-6 belong to another controller. When sending the INQUIRY command to lun 1, owned by the opposite controller, we got back the offline status. As above, the commandblocks would be re-used, and the original offline lun would continue to be queried, even when we should have moved on to the luns which -are- available on this controller. So, if lun 1 was offline, no luns were found on that channel. So in our case, we did not see ghost luns, but rather had missing luns. Glad to see you've fixed it, eagerly awaiting U6 :) -Eric Yes. It is kernel version 2.4.21-32.7.EL, and later. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-663.html |