Created attachment 346492 [details]
fix megaraid sas tape errors
Description of problem:
Megaraid SAS tape I/O errors on 'mt erase'. This is being fixed for RHEL5.4
vi BZ 475574, but that includes a full driver update - for RHEL4, we just
want the patch attached to this BZ to address the issues in the related IT.
How reproducible: always
Steps to Reproduce: 'mt erase' fails with I/O errors reported in syslog
The customer has verified the attached patch against 2.6.9-89.EL
fixes the issue on RHEL4.
I've started a brew build with patch http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1871969
Since I can't test it myself I'll then post a patched kernel here and ask you for verifying this.
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
the patched kernel is here http://people.redhat.com/thenzl/504080/
Please verify that it resolves the issue.
posted today - http://post-office.corp.redhat.com/archives/rhkernel-list/2009-July/msg00312.html
Committed in 89.10.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Time-outs resulted in I/O errors being logged to "/var/log/messages" when running "mt erase" on tape drives using certain LSI MegaRAID SAS adapters, preventing the command from completing. The megaraid_sas driver's timeout value is now set to the OS layer value.
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 therefore 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.