[5507] in RedHat Linux List
tape foolishness
daemon@ATHENA.MIT.EDU (bilker@bigfoot.com)
Thu Nov 21 20:06:57 1996
Date: Thu, 21 Nov 1996 17:06:11 -0800
To: redhat-list@redhat.com
From: bilker@bigfoot.com
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
Being somewhat timid from time to time, I bought my system pre-configured
for Linux from SWT. No complaints about SWT; the system came up right out
of the box and everything worked. It was shipped with 3.0.3 (kernel 2.0.0).
I've since upgraded to Colgate (BTW, I had few of the problems I've seen
reported here), and have added all the packages from the errata list.
However, since the upgrade the SCSI tape driver fails to properly close
the device (I think) after an async tape rewind. This results in an
uncompleted, uninterruptable syscall and process hang. Since the tape
device is (appears to be) exclusive open, I am limited to only 1 (ONE!)
tape operation between boots. I use the tape only for weekly dumps, so
I have to reboot at least every two weeks. (I.e., with my current usage
pattern the problem is more an annoyance than critical.)
[[ If not clear from the above, let me state explicitly that all of the
data movement to/from tape occurs --- I just can't get the command to exit
cleanly and free the device. ]]
A few details:
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HP Model: C3725S Rev: 6039
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SONY Model: CD-ROM CDU-76S Rev: 1.1c
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: HP Model: HP35470A Rev: T503
Type: Sequential-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: CDC Model: 94181-15 Rev: 5466
Type: Direct-Access ANSI SCSI revision: 01 CCS
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: CDC Model: 94171-9 Rev: 6261
Type: Direct-Access ANSI SCSI revision: 01 CCS
(Tape drive is HP35470A at SCSI ID 2)
--------------------- From the logfile (/var/log/messages) ---------------
Nov 20 10:06:25 sludge kernel: scsi : aborting command due to timeout : pid 198252, scsi0, channel 0, id 0, lun 0 Read (6) 13 fd c2 02 00
Nov 20 10:06:25 sludge kernel: scsi0 : DANGER : command running, can not abort.
Nov 20 10:06:28 sludge kernel: scsi : aborting command due to timeout : pid 198253, scsi0, channel 0, id 0, lun 0 Read (6) 13 3d d4 02 00
Nov 20 10:06:28 sludge kernel: scsi0 : found command 198253 in Linux issue queue
Nov 20 10:06:29 sludge kernel: scsi : aborting command due to timeout : pid 198254, scsi0, channel 0, id 0, lun 0 Read (6) 0f c4 36 08 00
Nov 20 10:06:29 sludge kernel: scsi0 : found command 198254 in Linux issue queue
[ ... snip ... ]
Nov 20 11:22:34 sludge kernel: + 60 : select_indirect = 0xc0000004
Nov 20 11:22:34 sludge kernel: + 56 : dsa_cmnd = 0x0
Nov 20 11:22:34 sludge kernel: + 48 : dsa_next = 0x0
Nov 20 11:22:34 sludge kernel: scsi0 : end schedule dsa array
Nov 20 11:22:34 sludge kernel: scsi0 : reconnect_dsa_head :
Nov 20 11:22:34 sludge kernel: scsi0 : end reconnect_dsa_head
Nov 20 11:22:34 sludge kernel: The sti() implicit in a printk() prevents hangs
Nov 20 11:22:34 sludge kernel: scsi0 : target 0 accepting asynchronous SCSI
Nov 20 11:22:34 sludge kernel: scsi0 : setting target 0 to asynchronous SCSI
Nov 20 11:22:43 sludge kernel: scsi : aborting command due to timeout : pid 324733, scsi0, channel 0, id 0, lun 0 Read (6) 0f c4 3e 08 00
Nov 20 11:22:43 sludge kernel: scsi0 : did this command ever run?
Nov 20 11:22:43 sludge kernel: scsi : aborting command due to timeout : pid 324734, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 26 fd c0 00 00 02 00
Nov 20 11:22:43 sludge kernel: scsi0 : did this command ever run?
-------------------------------------------------------
Any clues, anyone? Have I mis-configured something?
Thanks,
bilker@bigfoot.com
P.S. You may have noticed the old CDC disks in the list above -- these
are in an outboard box that I can turn off entirely. When I do so, the
tape symptoms described here are not altered a whit.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
