Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 161156

Summary: 'mt tell' fails - backported kernel bug likely
Product: Red Hat Enterprise Linux 4 Reporter: Mindy Preston <mpreston>
Component: kernelAssignee: Doug Ledford <dledford>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: bnocera, davej, jbaron
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2005-514 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 13:34:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 156322    
Attachments:
Description Flags
Fix for faulty return value none

Description Mindy Preston 2005-06-20 21:02:13 UTC
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 (
http://kerneltrap.org/node/4351 ).

Version-Release number of selected component (if applicable):

kernel-2.6.9-11.EL.SMP

How reproducible:

'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"
  
Actual results:

/dev/st0: No such device

Expected results:

The block # the tape is currently on

Additional info:

Comment 1 Jason Baron 2005-06-23 18:38:15 UTC
*** Bug 161335 has been marked as a duplicate of this bug. ***

Comment 4 Doug Ledford 2005-07-11 21:30:36 UTC
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.

Comment 5 Mindy Preston 2005-07-11 22:00:12 UTC
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.

Comment 6 Doug Ledford 2005-07-21 03:26:49 UTC
Patch committed to the U2 CVS tree, changing state to modified.

Comment 10 Red Hat Bugzilla 2005-10-05 13:34:10 UTC
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.

http://rhn.redhat.com/errata/RHSA-2005-514.html