Bug 49379
Summary: | Unable to open() a disconnected LUN | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Wayne Berthiaume <berthiaume_wayne> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | berthiaume_wayne, dledford |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:39:05 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
Wayne Berthiaume
2001-07-18 20:06:31 UTC
Have just completed testing on RH6.2 lk 2.2.16-3 and a disconnected LUN can be openned by sg(). Tested RH7.0 lk 2.2.16-22, 2.2.17-14, and 2.2.19-7.0.1 and they all fail when sg tries to open the disconnected LUN. I further tested RH7.1 lk 2.4.2-2 and was unable to open the disconnected LUN. All failures were the same as above. I still suspect the change that is causing the problem occured in the SCSI midlayer used in RH7.0 and 7.1. We've turned on SCSI logging in hopes of gathering further information but can't seem to figure out how to get useful information out of the debugging information. We're using the scan token believing the problem exist somewhere in this area of the code. One of the problems we're encounteing with SCSI logging is we have multiple Qlogic QLA/2200FC HBA's in the system so the information that is pushed to /var/log/messages from one HBA gets step on by the other HBA so it is not complete and, at times, isn't intelligible. I hope this additional information we provide further insight into the problem. Doug: any ideas ? Yeah, I'm pretty sure what the problem is, and what patch exactly caused it. The linux-2.4.2-scsi_scan.patch in the 2.4 kernel RPM is the cause of the problem. However, it went in specifically to solve another problem (some device report lots of offline drives in the sparse space, including the Clarrion arrays that Wayne is using, so that if you don't include this patch, you end up with 254 offline entries in the SCSI device list on some arrays). In short, it's an inconsistent usage of the offline status in the SCSI Inquiry data that is causing this problem and I don't see any good answer. With the patch you have problems, and without the patch you have problems. My preferred choice is to leave the patch and make configuration tools go through whatever device is at LUN0 on the chassis for proper configuration, but I don't know enough about the current setup Wayne is using to say if that's possible. Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |