ADSM-L

ADSM 3.1.2.0 crashing on Sun 2.6

1998-12-20 18:12:38
Subject: ADSM 3.1.2.0 crashing on Sun 2.6
From: Timo Heinonen <Timo.Heinonen AT NMP.NOKIA DOT COM>
Date: Mon, 21 Dec 1998 01:12:38 +0200
Hi,

I have been testing ADSM V3.1.2.0 on Sun Solaris 2.6, UE5000 with STK
ACSLS 5.2 and 9740 with 10 DLT 7000 drives. Everything was quite smooth
until last week when ADSM started to crash almost every time it tried to
do something related to library or drives. I suppose that this is STK
and ACSLS problem, but ADSM should not crash in these situations.

How could I trace further what is causing the problems and is there
something I could do to correct the situation? I know that there is some
enhancements in 3.1.2.1 version related to ACSLS, but is there something
that could help me?

in messages file there is message:
Dec 20 16:30:03 adsm03 unix: NOTICE: mt@3,0:
scsi_cmd=16,errno=5,cc=210,sense=70  0  6  0  0  0  0 16  0  0  0  0 29
0  0  0  0  0 82  1

In act log there are messages:
ANR8775I Drive DRV2 (/dev/rmt/9mt) unavailable at library manager.
... some other messages ...
ANR8797W Drive DRV2 of library STK9740 is inaccessible; server has begun
ANR8797W polling drive.
ANR7821S Thread 36 (tid 128) terminating on signal 11 (Segmentation
violation).
ANR9999D Trace-back of called functions:
ANR9999D   0x000639BC  AbortServer
ANR9999D   0x00063EB4  TrapHandler
ANR9999D   0xEF6D2EBC  *UNKNOWN*
ANR9999D   0xEF6D22D0  *UNKNOWN*
ANR9999D   0x005E0100  DrivePollThread
ANR9999D   0x00063BA8  StartThread
ANR9999D   0xEF6D4BDC  *UNKNOWN*
ANR9999D   0x00063AD0  StartThread


Messages from previous crash


ANR8302E I/O error on drive DRV6 (/dev/rmt/7mt) (OP=READ, CC=203,
KEY=02, ANR8302E ASC=04, ASCQ=02,
SENSE=F0.00.02.00.04.00.00.16.00.00.00.00.04.02.00.0-
ANR8302E 0.00.00.82.01.01.00.00.14.12.00.00.00.00., Description=Manual
ANR8302E intervention required).  Refer to Appendix B in the 'Messages'
Manual
ANR8302E for recommended action.
ANR8302E I/O error on drive DRV6 (/dev/rmt/7mt) (OP=LOCATE, CC=203,
KEY=02,
ANR8302E ASC=04, ASCQ=02,
SENSE=70.00.02.00.00.00.00.16.00.00.00.00.04.02.00.0-
ANR8302E 0.00.00.82.01.01.00.00.14.12.00.00.00.00.,
Description=Manual
ANR8302E intervention required).  Refer to Appendix B in the 'Messages'
manual
ANR8302E for recommended action.
... some other messages ...
ANR8797W Drive DRV2 of library STK9740 is inaccessible; server has begun
ANR8797W polling drive.
ANR7821S Thread 69 (tid 121) terminating on signal 11 (Segmentation
violation).
ANR9999D Trace-back of called functions:
ANR9999D   0x000639BC  AbortServer
ANR9999D   0x00063EB4  TrapHandler
ANR9999D   0xEF6D2EBC  *UNKNOWN*
ANR9999D   0xEF6D22D0  *UNKNOWN*
ANR9999D   0x005E0100  DrivePollThread
ANR9999D   0x00063BA8  StartThread
ANR9999D   0xEF6D4BDC  *UNKNOWN*
ANR9999D   0x00063AD0  StartThread

Messages about other crashes seem alike.

The reason for using ACSLS is STK's support for 6 integrated 9740
modules with "PTP" (Pass Through Port, I don't know how they call it
today, I know they have changed it's name). Will it be supported by
ADSM?

BR:

Timo Heinonen
<Prev in Thread] Current Thread [Next in Thread>
  • ADSM 3.1.2.0 crashing on Sun 2.6, Timo Heinonen <=