Bård Tesaker wrote:
>
> Hi!
>
> My experience is that the tape drive issues a CAM event for almost
> anything. Just a fsf beond the EndOfData will submit one.
>
> You may get more out of it by giving "-o full" to uerf
I didn't know this option (-o full) here is the output:
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 196.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Sep 28 11:56:03 2001
OCCURRED ON SYSTEM drp01
SYSTEM ID x0007001E
SYSTYPE x00000000
----- UNIT INFORMATION -----
CLASS x0001 TAPE
SUBSYSTEM x0000 DISK
BUS # x0003
x00C8 LUN x0
TARGET x1
----- CAM STRING -----
ROUTINE NAME ctape_move_tape
----- CAM STRING -----
ERROR TYPE Hard Error Detected
----- CAM STRING -----
DEVICE NAME DEC TZ89 (C) DEC2150
----- CAM STRING -----
Active CCB at time of error
----- CAM STRING -----
CCB request completed with an
error
----- ENT_CCB_SCSIIO -----
*MY ADDR x05A9DE80
CCB LENGTH x00C0
FUNC CODE x01
CAM_STATUS x00C4 CAM_REQ_CMP_ERR
SIM QFRZN
AUTOSNS_VALID
PATH ID 3.
TARGET ID 1.
TARGET LUN 0.
CAM FLAGS x000000C0
CAM_DIR_NONE
*PDRV_PTR x05A9DB28
*NEXT_CCB x00000000
*REQ_MAP x00000000
VOID (*CAM_CBFCNP)() x004856F0
*DATA_PTR x00000000
DXFER_LEN x00000000
*SENSE_PTR x05A9DB50
SENSE_LEN x48
CDB_LEN x06
SGLIST_CNT x0000
CAM_SCSI_STATUS x0002 SCSI_STAT_CHECK_CONDITION
SENSE_RESID x2A
RESID x00000000
CAM_CDB_IO x00000000000000FFFFFF0111
CAM_TIMEOUT x00000E10
MSGB_LEN x0000
VU_FLAGS x0000
TAG_ACTION x00
----- CAM STRING -----
Error, exception, or abnormal
_condition
----- CAM STRING -----
NOT READY - Logical unit is NOT
ready
----- ENT_SENSE_DATA -----
ERROR CODE x0070 CODE x70
SEGMENT x00
SENSE KEY x0002 NOT READY
INFO BYTE 3 x00
INFO BYTE 2 x00
INFO BYTE 1 x00
INFO BYTE 0 x00
ADDITION LEN x16
CMD SPECIFIC 3 x00
CMD SPECIFIC 2 x00
CMD SPECIFIC 1 x00
CMD SPECIFIC 0 x00
ASC x04
ASQ x02
FRU x00
SENSE SPECIFIC x000000
ADDITIONAL SENSE
0000: 00460082 00824200 00000000 00000000 *..F..B..........*
0010: 00000000 00000000 00000000 00000000 *................*
0020: 00000000 00000000 00000000 00000000 *................*
0030: 00000000 00000000 7E250000 00005E3C *..........%~<^..*
0040: 00000000 00000000 *........ *
Christian.
> BT
>
> On Tue, 2 Oct 2001, Christian Biache wrote:
>
> >
> > Hi managers!
> >
> > I need help to understand what's going on:
> >
> > ********************************* ENTRY 1.
> > *********************************
> >
> > ----- EVENT INFORMATION -----
> >
> > EVENT CLASS ERROR EVENT
> > OS EVENT TYPE 199. CAM SCSI
> > SEQUENCE NUMBER 196.
> > OPERATING SYSTEM DEC OSF/1
> > OCCURRED/LOGGED ON Fri Sep 28 11:56:03 2001
> > OCCURRED ON SYSTEM drp01
> > SYSTEM ID x0007001E
> > SYSTYPE x00000000
> >
> > ----- UNIT INFORMATION -----
> >
> > CLASS x0001 TAPE
> > SUBSYSTEM x0000 DISK
> > BUS # x0003
> > x00C8 LUN x0
> > TARGET x1
> >
> >
> > ********************************* ENTRY 2.
> > *********************************
> >
> > ----- EVENT INFORMATION -----
> >
> > EVENT CLASS ERROR EVENT
> > OS EVENT TYPE 100. CPU EXCEPTION
> > SEQUENCE NUMBER 184.
> > OPERATING SYSTEM DEC OSF/1
> > OCCURRED/LOGGED ON Fri Sep 28 10:02:17 2001
> > OCCURRED ON SYSTEM drp01
> > SYSTEM ID x0007001E
> > SYSTYPE x00000000
> >
> > ----- UNIT INFORMATION -----
> >
> > UNIT CLASS CPU
> >
> >
> > ********************************* ENTRY 3.
> > *********************************
> >
> > ----- EVENT INFORMATION -----
> >
> > EVENT CLASS OPERATIONAL EVENT
> > OS EVENT TYPE 300. SYSTEM STARTUP
> > SEQUENCE NUMBER 0.
> > OPERATING SYSTEM DEC OSF/1
> > OCCURRED/LOGGED ON Thu Sep 27 03:28:40 2001
> > OCCURRED ON SYSTEM drp01
> > SYSTEM ID x0007001E
> > SYSTYPE x00000000
> > MESSAGE Alpha boot: available memory
> > from
> > _0xb5e000 to 0xfffe000
> > Digital UNIX V4.0F (Rev. 1229);
> > Wed
> > _May 16 10:49:23 GMT 2001
> > physical memory = 256.00 megabytes.
> > available memory = 244.77 megabytes.
> > using 975 buffers containing 7.61
> > _megabytes of memory
> > Digital Personal WorkStation 500au
> > Firmware revision: 6.9-7
> > PALcode: Digital UNIX version 1.22-0
> > [available upon request]
> > isp1 at pci1000 slot 8
> > isp1: QLOGIC ISP1040B/V2
> > isp1: Firmware revision 5.57 (loaded
> > _by console)
> > isp1: Fast RAM timing enabled.
> > scsi3 at isp1 slot 0
> > tz25 at scsi3 target 1 lun 0 (LID=2)
> > _(DEC TZ89 (C) DEC 2150)
> > _(Wide16)
> > tz28 at scsi3 target 4 lun 0 (LID=3)
> > _(DEC TZ89 (C) DEC 2150)
> > _(Wide16)
> > [available upon request]
> >
> > --- snip snip ---
> >
> > The CAM SCSI errors occurs in 4 different machines sometimes preceded
> > by the CPU error. It seems that this problem is trigged by our
> > backup software when writing to the tape.
> >
> > The 4 machines has the same hardware configuration and run the same
> > software.
> >
> > Drives and controllers were replaced with new ones but the problem
> > is still there.
> >
> > TIA,
> >
> > Christian.
> >
> >
> > --
> > |<- Christian Biache Christian.Biache_at_thalesatm.com ->|
> > |<-Thales ATM - 19, rue de la Fontaine - 92221 Bagneux Cedex - France->|
> > |<- http://www.thalesatm.com ->|
> >
>
> Bård Tesaker "Are you satisfied with the backup" -- vmsinstal
> ------------------------------------------------------------------------
> ED-tjenesten, Rom C2-116b, Realfagbygget phone: +47 73591798
> NTNU, Fak. for Kjemi og biologi
> N-7491 Trondheim bard.tesaker_at_chembio.ntnu.no
--
|<- Christian Biache Christian.Biache_at_thalesatm.com ->|
|<-Thales ATM - 19, rue de la Fontaine - 92221 Bagneux Cedex - France->|
|<- http://www.thalesatm.com ->|
Received on Tue Oct 02 2001 - 13:20:46 NZST