Bug 427576
| Summary: | Reading/writing a tape drive sometimes fails with scsi errors | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Kern Sibbald <kern> | ||||
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.1 | CC: | coughlan | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-30 12:47:03 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
Kern Sibbald
2008-01-04 20:52:58 UTC
Created attachment 290859 [details]
scsi errors found in /var/log/messages corresponding to failures
In checking back on the previous SuSE kernel problem, it was in kernel 2.6.16 and so is not related to this bug. This is a bit complicated and I am still analyzing it, but it looks like while one thread is doing write() operations to the drive another thread calls mtx which removes the tape from the drive. That causes the kernel tape driver to get confused, and thereafter even though the drive is close()ed and open()ed again, it fails to work always getting either a Resource is Busy or an I/O Error. The only way I have found to be able to re-use the drive is to reboot. If you have any less drastic way of clearing the kernel driver, I would like to know. In addition, despite what I previously said, it seems to occur on both kernels mentioned, though I cannot reproduce it on later kernels (SuSE 10.2). (In reply to comment #2) > If you have any less drastic way of clearing the kernel driver, I would like > to know. I assume you tried rmmod st.ko ? From the messages "Dumping Card State" it appears you have an aic* HBA. You should rmmod/insmod that as well to try to clear the error. > In addition, despite what I previously said, it seems to occur on both kernels > mentioned, though I cannot reproduce it on later kernels (SuSE 10.2). So, kernel-2.6.18-53.1.4.el5 fails. Please try a newer kernel-2.6.18...el5 version. This bugzilla is really old and there has been no reply to Tom's questions for years, so taking the liberty to close it. If you experience similar problems with a newer version of RHEL, please open a new bugzilla. Jes |