On Fri, 1 Jan 1999, Guest section DW wrote:
>
> Maybe you can show in plain text what is wrong?
> (If it is hundreds of kilobytes a URL should be given.
> If it is not more than a hundred lines or so, plaintext
> is much better than something that cannot be read without
> additional effort.)
>
>
> Let me conjecture: You read a tape, get a timeout, say while rewinding -
> the scsi layer sees an error and tries to correct it, using abort,
> bus device reset, scsi bus reset, host reset...
>
>
> The end result depends on what driver you are using.
> What happened in your case?
>
Sorry - I don't know why the attachment was in MIME format. Here are the
relevant parts from dmesg:
scsi0: Target 0: Queue Depth 28, Synchronous at 10.0 MB/sec, offset 15
scsi0: Target 1: Queue Depth 3, Synchronous at 10.0 MB/sec, offset 15
scsi0: Target 5: Queue Depth 3, Asynchronous
scsi : detected 1 SCSI tape 1 SCSI cdrom 1 SCSI disk total.
st: Buffer size 32768 bytes, write threshold 30720 bytes.
st: Allocated tape buffer 0 (32768 bytes, 1 segments, dma: 1, a:
c0ff0000).
st: segment sizes: first 32768, last 32768 bytes.
st: Allocated tape buffer 1 (32768 bytes, 1 segments, dma: 1, a:
c0fe8000).
st: segment sizes: first 32768, last 32768 bytes.
scsi0: Tagged Queuing now active for Target 0
st0: Block limits 1 - 65536 bytes.
st0: Mode sense. Length 14, medium 0, WBS 10, BLL 8
st0: Density 11, tape length: 0, drv buffer: 1
st0: Block size: 1024, buffer size: 32768 (32 blocks).
st0: Flushing 10240 bytes.
st0: File length 10240 bytes.
st0: Async write waits 0, finished 0.
st0: Buffer flushed, 1 EOF(s) written
st0: Rewinding tape.
st0: Block limits 1 - 65536 bytes.
st0: Mode sense. Length 14, medium 0, WBS 10, BLL 8
st0: Density 11, tape length: 0, drv buffer: 1
st0: Block size: 1024, buffer size: 32768 (32 blocks).
st0: Flushing 10240 bytes.
st0: File length 16691200 bytes.
st0: Async write waits 540, finished 3.
st0: Buffer flushed, 1 EOF(s) written
st0: Rewinding tape.
st0: Block limits 1 - 65536 bytes.
st0: Mode sense. Length 14, medium 0, WBS 10, BLL 8
st0: Density 11, tape length: 0, drv buffer: 1
st0: Block size: 1024, buffer size: 32768 (32 blocks).
st0: Error: 28000002, cmd: 8 1 0 0 20 0 Len: 32768
FMK Current error st09:00: sense key None
st0: Sense: f0 0 80 0 0 0 14 6
st0: EOF detected (12288 bytes read).
st0: EOF up (1). Left 12288, needed 2048.
st0: EOF/EOM flag up (1). Bytes 10240
st0: EOF up (1). Left 10240, needed 10240.
st0: Rewinding tape.
scsi : aborting command due to timeout : pid 3870, scsi0, channel 0, id
0, lun 0
Read (10) 00 00 24 5c 90 00 00 08 00
scsi0: Aborting CCB #3883 to Target 0
SCSI host 0 abort (pid 3870) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Sending Bus Device Reset CCB #3885 to Target 0
SCSI host 0 channel 0 reset (pid 3870) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 0
scsi0: Resetting BusLogic BT-958 Failed
SCSI host 0 reset (pid 3870) timed out again -
probably an unrecoverable SCSI bus or device hang.
scsi : aborting command due to timeout : pid 3871, scsi0, channel 0, id
0, lun 0
Write (6) 0f 90 14 02 00
scsi0: Unable to Abort Command to Target 0 - CCB Reset
SCSI host 0 abort (pid 3871) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 0
wait_on_bh, CPU 0:
irq: 0 [0 0]
bh: 1 [0 1]
scsi0: Resetting BusLogic BT-958 Failed
SCSI host 0 channel 0 reset (pid 3871) timed out - trying harder
SCSI bus is being reset for host 0 channel 0.
scsi0: Resetting BusLogic BT-958 due to Target 0
scsi0: Resetting BusLogic BT-958 Failed
SCSI host 0 reset (pid 3871) timed out again -
probably an unrecoverable SCSI bus or device hang.
I've put some printk's to st.c and found that it does indeed get stuck
while trying to do a close on the device.
After this the system goes through cycles of responsiveness and no
response. The load skyrockets.
Here is what /proc/scsi/scsi has to say:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST11950N Rev: 0009
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: TOSHIBA Model: CD-ROM XM-6201TA Rev: 1030
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: ARCHIVE Model: VIPER 2525 25583 Rev: -002
Type: Sequential-Access ANSI SCSI revision: 01
Let me know what more I can do.
James Rich
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]