From: James Rich <[EMAIL PROTECTED]>
To: linux-scsi <[EMAIL PROTECTED]>
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable
You are quite right.
I have more on the reading tapes problem I reported earlier. I changed
#DEFINE debug 0 to 1 and recompiled. I have more error messages as I
also enabled verbose scsi error reporting. Attached is the output of
dmesg after the tape read operation fails. Notice that the tape does
read all the files ok, but then has troubles ending the operation.
James Rich
[EMAIL PROTECTED]
c2NzaTA6IFRhcmdldCAwOiBRdWV1ZSBEZXB0aCAyOCwgU3luY2hyb25vdXMg
YXQgMTAuMCBNQi9zZWMsIG9mZnNldCAxNQ0Kc2NzaTA6IFRhcmdldCAxOiBR
dWV1ZSBEZXB0aCAzLCBTeW5jaHJvbm91cyBhdCAxMC4wIE1CL3NlYywgb2Zm
c2V0IDE1DQpzY3NpMDogVGFyZ2V0IDU6IFF1ZXVlIERlcHRoIDMsIEFzeW5j
...
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?
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
