Description of problem: When attaching STK T10000 tape drives to a RHEL5 host via direct FC connection the drives fail to operate correctly. Different failure rates are seen with different versions of the driver: Success rate Driver version 20% 8.01.04 95% 8.01.07-k6 100% 8.02.08 Version-Release number of selected component (if applicable): Tested with 2.6.18-94.el5. This produced the highest success rate of the tested RHEL kernels to date. Tests with the QLogic provided driver version 8.02.08 produced a 100% success rate. How reproducible: Unknown Steps to Reproduce: Unknown Actual results: Failures seen as stated in table above. Expected results: Failures should be extremely rare or non-existant. Additional info:
At 04:28 PM 6/10/2008, Ben Woodard wrote: >Can you explain the problem with the qla2xxx driver again. My >understanding was that older drivers were not seeing all the devices >on the FC fabric. Is that right or were you seeing problems after >the devices appeared? > >-ben Yes, that's correct. At 8.1.4 we were getting successful drive configs (entries in /dev and /proc/scsi/scsi) about 20% of the time. Not good. At version 8.1.7, we were getting successful configs 90ish%. Once we got v8.2.8, we saw 100%. What's important to understand about our environment - and potentially why other sites don't see this problem - is because our devices are directly connected to the Q-Logic HBAs. No intermediate switching technology. It also may be related to our specific device, the Sun/STK T10000 tape drive with the 4Gbps optics. -Todd Internal Status set to 'Waiting on Engineering' This event sent from IssueTracker by kbaxley issue 184281
The failure cases mentioned in comment #0 refer to times when the device fails to be detected/configured automatically, i.e.: - no entry in /proc/scsi/scsi - no device nodes created
(In reply to comment #3) > The failure cases mentioned in comment #0 refer to times when the device fails > to be detected/configured automatically, The next steps would be to: 1. See if the tape drive will be detected after boot time. Something like: echo 1 > /sys/class/fc_host/host1/issue_lip echo 1 > /sys/class/scsi_host/host1/scan 2. Run with the ql2xextended_error_logging mod param set to 1. 3. Provide /var/log/messages showing the failure. Marcus, please inquire whether anyone at QLogic has access to a Sun/STK T10000 tape drive with 4Gbps. Ask them to try this, direct connect.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
An update on this please? Does the 5.3 beta solve this? If not, reply to comment 4?
Bryn - any updates to this? Are you still seeing this?
Updating PM score.
This issue will now be closed due to inactivity.