[6134] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

sense key Illegal Request

daemon@ATHENA.MIT.EDU (Juergen Leising)
Fri Mar 19 14:58:05 1999

Date: 	Fri, 19 Mar 1999 16:26:44 +0100
From: Juergen Leising <a0037@stud.uni-bayreuth.de>
To: linux-scsi@vger.rutgers.edu
Reply-To: Juergen Leising <a0037@stud.uni-bayreuth.de>


Hello to everybody,

during my daily backup run by crond some errors occured. Unfortunately I
don't know how severe they are and if I should do anything against them.
My backup script has worked successfully for several days using the recent tape;
backup and verification didn't provoke any problems up to now. Well - up to now...

Actually, I faced to errors:

1. mt -f /dev/nst0 seod didn't really space to eod, but stopped at the first third of its way, yet.
2. afio couldn't continue writing to tape.

My setup: 

SCSI controller: Dawicontrol 2975U
Tape drive: Tandberg NS 20 PRO (actually it is 10 GB uncompressed)
Tape: Imation (former 3M) Travan NS 20 (10 GB uncompressed)
OS: Redhat 5.2, kernel 2.2.3
tape utilities: mt-st-0.4-5

command to be performed:  afio -ofzBZv -M 50m -G 6 -T 3k -b32k -c1024 -s10g
preceding commands:  mt -f /dev/nst0 seod ; mt -f /dev/nst0 tell

The seod command failed as well - as I can read from the tell result the tape
didn't really go to eod, but stopped at approximately the first third of the tape.
So maybe afio trying to write to tape couldn't do that, because it would have
overwritten an already existing archive. If this assumption is true, the real
question is, why mt seod failed.  But I stress: These are presumptions - not
real knowledge.

Can somebody please tell me, what those errors mean and how I can avoid them?


Excerpt from /var/log/messages:

(...)
Mar 18 11:04:24 jl2 kernel: ncr53c8xx: at PCI bus 0, device 9, function 0
Mar 18 11:04:24 jl2 kernel: ncr53c8xx: 53c876 detected
Mar 18 11:04:24 jl2 kernel: ncr53c876-0: rev=0x26, base=0xe9001000, io_port=0xe800, irq=9
Mar 18 11:04:24 jl2 kernel: ncr53c876-0: ID 7, Fast-20, Parity Checking
Mar 18 11:04:24 jl2 kernel: ncr53c876-0: on-chip RAM at 0xe9000000
Mar 18 11:04:24 jl2 kernel: ncr53c876-0: restart (scsi reset).
Mar 18 11:04:24 jl2 kernel: ncr53c876-0: Downloading SCSI SCRIPTS.
Mar 18 11:04:24 jl2 kernel: scsi0 : ncr53c8xx - revision 3.1h
Mar 18 11:04:24 jl2 kernel: scsi : 1 host.
Mar 18 11:04:24 jl2 kernel:   Vendor: TANDBERG  Model:  NS20 Pro 20 GB   Rev: 7.14
Mar 18 11:04:24 jl2 kernel:   Type:   Sequential-Access                  ANSI SCSI revisi
on: 02
Mar 18 11:04:24 jl2 kernel: Detected scsi tape st0 at scsi0, channel 0, id 0, lun 0
Mar 18 11:04:24 jl2 kernel: scsi : detected 1 SCSI tape total.

(...)

Mar 18 19:10:01 jl2 kernel: ncr53c876-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
Mar 18 19:24:23 jl2 -- MARK --
Mar 18 19:40:04 jl2 kernel: st0: Error with sense data: Current error st09:00: sense key
Illegal Request
Mar 18 19:42:17 jl2 kernel: st0: Error with sense data: extra data not valid Current erro
r st09:00: sense key Illegal Request
Mar 18 19:42:17 jl2 kernel: st0: Error on write filemark.
Mar 18 19:58:27 jl2 kernel: scsi : aborting command due to timeout : pid 41, scsi0, chann
el 0, id 0, lun 0 Read (6) 01 00 00 40 00
Mar 18 19:58:27 jl2 kernel: ncr53c8xx_abort: pid=41 serial_number=56 serial_number_at_tim
eout=56
Mar 18 19:58:28 jl2 kernel: SCSI host 0 abort (pid 41) timed out - resetting
Mar 18 19:58:28 jl2 kernel: SCSI bus is being reset for host 0 channel 0.
Mar 18 19:58:28 jl2 kernel: ncr53c8xx_reset: pid=41 reset_flags=2 serial_number=56 serial
_number_at_timeout=56
Mar 18 19:58:28 jl2 kernel: ncr53c876-0: restart (scsi reset).
Mar 18 19:58:28 jl2 kernel: ncr53c876-0: Downloading SCSI SCRIPTS.
Mar 18 19:58:28 jl2 kernel: ncr53c876-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
Mar 18 19:58:29 jl2 kernel: st0: Error with sense data: extra data not valid Current erro
r st09:00: sense key Unit Attention
Mar 18 19:58:29 jl2 kernel: Additional sense indicates Power on, reset, or bus device res
et occurred
(...)

Up to now the mentioned problem hasn't occured any more - but I would like to
know if this a severe problem or not.

Any help would be appreciated,

bye, bye, Juergen.


-- 
*****************************************************************
* Juergen Leising, E-Mail: juergen.leising@stud.uni-bayreuth.de *
*          http://www.stud.uni-bayreuth.de/~a0037/              *
*****************************************************************

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post