Bug 410231 - st tape device /dev/st0l doesn't work anymore
st tape device /dev/st0l doesn't work anymore
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.5
i686 Linux
low Severity high
: ---
: ---
Assigned To: Red Hat Kernel Manager
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-04 07:29 EST by starlight
Modified: 2012-06-20 11:58 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 11:58:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description starlight 2007-12-04 07:29:35 EST
Description of problem:

Sometime in the last few releases /dev/st0l and /dev/nst0l
stopped working.  Probably /dev/st0[am] and /dev/nst[am]
don't work anymore either.

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

2.6.9-55.0.12.EL

How reproducible:

tar -f /dev/st0l

Actual results:

Variety of strange random messages in 'dmesg'.
Changes ever time.  Here's a good one:

st0: Block limits 2 - 16777214 bytes.                                           
(scsi0:A:0:0): Unexpected busfree in Command phase, 1 SCBs aborted, PRGMCNT ==
>>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
scsi0: Dumping Card State at program address 0x197 Mode 0x11
Card was paused

Expected results:

It should work.

Additional info:

/dev/st0 work just fine.  /dev/st0l *definitely* used to work.

Drive:  Quantum VS160
SCSI: Adaptec 39320A
Comment 1 Jiri Pallich 2012-06-20 11:58:03 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.