Bug 170499
Summary: | mt exitcodes wrong with ide tapedrive | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | koen05 <bugzilla> |
Component: | mt-st | Assignee: | Jindrich Novy <jnovy> |
Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | pknirsch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-10-31 11:11:11 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
koen05
2005-10-12 13:25:25 UTC
- FC4 lives on a SATA raid 1 - Tapestreamer is connected to the IDE port - When connected to USB (via an IDEtoUSB-converter), mt wil give the correct status (mt -f /dev/st0 status), but fails to detect that there is no tape in the drive when doing a mt -f /dev/st0 rewind. Do you see this behavior also with the rawhide mt-st installed? (latest devel mt-st-0.9b is now built in devel) I'll release FC updates if it solves the problem for you. I've compiled mt-st-0.9b from source, same results as FC4's mt-st-0.8 I suspect (after googl'ing for some time) it has got to do with the Intel ICH6R/ICH6RW Sata controler being in dual mode (IDE for the dvdrom and tapestreamer and SATA for the disks). Perhaps i'll try to find a SATA to IDE converter later this week so i can attach the tapestreamer to an Sata channel. I've just upgraded the box to kernel-2.6.13-1.1532_FC4.i686 mt exitcodes seem to be fixed! mt -f /dev/st0 rewind does however take a very long time to discover that there's no tape in the drive. Will do further tests on monday. Ok, FC4 update is comming soon. From User-Agent: XML-RPC mt-st-0.9b-1.fc4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. |