Description of problem:
A SCSI tape drive can be read from and written to, but the command 'mt tell'
fails with 'no such device', even when the correct device is specified. 'mt
tell' succeeded with the same machine and tape drive under a 2.4 kernel and
earlier Red Hat release. I believe this is a kernel issue that was backported
into 2.6.9 because it is mentioned on kerneltrap.org (
Version-Release number of selected component (if applicable):
'mt -f <scsi device> tell'
Steps to Reproduce:
1. attach a SCSI drive to the system
2. "dmesg | grep Attached" to get the proper device
3. confirm read/write from that device succeed, as well as other mt commands
4. "mt tell"
/dev/st0: No such device
The block # the tape is currently on
*** Bug 161335 has been marked as a duplicate of this bug. ***
Created attachment 116629 [details]
Fix for faulty return value
This should be all that's needed to solve the problem. I don't have a tape
drive in my test system, so any testing of this would be appreciated.
I have since moved the tape drive to a different machine, since the user needed
access to some data saved on DLTs. Unfortunately, I won't be able to test this
for you in the near future.
Patch committed to the U2 CVS tree, changing state to modified.
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 the 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.