Bug 179474
| Summary: | Problem with multiple SCSI LUNs and aic7xxx | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | wilburn | ||||||
| Component: | kernel | Assignee: | Tom Coughlan <coughlan> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.0 | CC: | alriddoch, coldwell, jbaron | ||||||
| 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: | 2006-02-17 13:59:20 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
wilburn
2006-01-31 17:33:17 UTC
Created attachment 123926 [details]
dmesg output
As a test, moved the RAID arrays and SCSI card to a machine running RHEL3. Everything works. Attached is dmesg output for this case. Created attachment 124645 [details]
dmesg output (RHEL3)
One of the differences between RHEL 3 and 4 is that RHEL 4 uses the Report LUN command. It looks like this storage device is returning bad info in response to this command. You can turn of the Report LUN probing, and revert to one-at-a-time scanning by setting the device_info flag: 0x40000 /* don't try REPORT_LUNS scan (SCSI-3 devs) */ with the command: echo 'CAEN RAP':'TOR 16':0x40000 > /proc/scsi/device_info Now rmmod/modprobe the aic7xxx driver. If this does not work, turn on the debug messages and report the results: sysctl -w dev.scsi.logging_level=0x000001c0 rmmod/modprobe the aic7xxx driver. This fixes the problem. Does this mean it is a problem with the RAID device, rather than a bug? So far we know that the data returned by the RAID device in response to the Report LUNs command is not interpreted correctly by Linux. It seems likely that the problem is with the data, since Linux handles the Report LUN data from every other known RAID device correctly. Someone would need to look at the data returned to see if it meets the SCSI spec. There is another indication that this device may not be carefully adhering to the SCSI spec. This information: Vendor: CAEN RAP Model: TOR 16 Comes from the RAID box's reply to the SCSI Inquiry command. The Vendor ID is defined as 8 bytes of ASCII data, and the Product ID (Model) field is defined as 16 bytes of ASCII data. I suspect that the Model is supposed to be "RAPTOR 16", but they did not bother fill the Vendor field so that the Model field is aligned properly. I'll close this, since you have a workaround. If you find that the device is actually complying with the SCSI spec. you can re-open it. |