[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::sls

Title:Storage Library System
Moderator:COOKIE::REUTER
Created:Sun Oct 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2270
Total number of notes:7850

2200.0. "SYSTEM-F-ACCVIO after resuming operation on 2nd volume" by CSC32::V_HEINICKE () Tue Feb 18 1997 15:00

Hi,

SLS V2.8-eco2
VMS 5.5-2
TA90
                                    
A customer stated that he has been seening SYSTEM-F-ACCVIOs in SBK files
for quite a few years (all different versions of SLS).  The accvio's
happen infrequently and he has never been able to determine the cause.  

The following happened recently.  The accvio occurred after at least 5 of the 
Files_n had completed successfully.  The 2nd volume was mounted and it stated
the operation was resuming and then immediately came back with an ACCVIO.  
The next files_n completed successfully.

Is this possibly a quota problem?

Following is the information from the accvio.

The customer, Jim Kelly, stated that this has happened infrequently over the 
years but has never been pinpointed.

I do have the complete log file if you would like to see it.

Any help would be geatly appreciated.

Thanks,

Victoria

$       WRITE SYS$OUTPUT -
"******* Beginning subprocess output for FILES_5 *******"
******* Beginning subprocess output for FILES_5 *******
$       TYPE SLS$ROOT:[SYSBAK.SYSBAK_LOGS]SYSBAK_20A0A3AC_5.LOG;1
$!
$!*  COPYRIGHT (c) 1993 BY DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS.
$!
$!
$!      S L S $ S Y S B A K _ S P A W N . C O M
$! 
$! This procedure issues the RUN command on the SYSBAK.EXE image after
$! settting appropriate process parameters.
$!
$ set verify
$ set process/dump
$ run/NODEBUG sls$system:sls$sysbak.exe
%SLS-I-FOLLOWS, volume M00610 follows M00812
%SLS-I-STARTING, starting volume M00610 at position 3 on drive _$1$MUA1: at 17-FEB-1997 22:21:12.43
%SLS-I-FOLLOWS, volume M00551 follows M00610
%SLS-I-FOLLOWS, volume M00626 follows M00551
%SLS-I-FOLLOWS, volume M01050 follows M00626
$ V = 1
$ SET NOON
$ ASSIGN _MBA848: SYS$COMMAND
$ ASSIGN _MBA850: SYS$ERROR
$ SET COMMAND SLS$SYSTEM:BACKUPCMD.CLD
$ ASSIGN SLS$SYSTEM:VMSBUXX.EXE; BACKUP
$ RUN/NODEBUG SLS$SYSTEM:SLS$LOAD_FINALSTS.EXE
$ -
BACK/LIST=_MBA853:/FULL -
DISK$SHAR3:/IMAG/RECO/IGNOR=(LABE,INTER)/EXCLUDE=(*.LOG) -
_$1$MUA1:DISK$SHAR3.BAK,_$1$MUA2:,_$1$MUA3:,_$1$MUA4:/PROT=(S:RW,O:RW,G:R,W:R)/NOASSI
%SLS-I-FINISHED, finished volume M00610 on drive _$1$MUA1: at 17-FEB-1997 22:24:06.19
%SLS-I-STARTING, starting volume M00551 at position 0 on drive _$1$MUA2: at 17-FEB-1997 22:24:06.59
%BACKUP-I-RESUME, resuming operation on volume 2
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000001E, 
PC=00017361, PSL=03C00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00000000
        Name   = 0000000C                2FFC0000
                 00000000                7FE1C2B0
                 0000001E                7FE1C290
                 00017361                0001199A
                 03C00004                00000023
                                         000004A4
                                         00010391
                                         00000934
                                         00010733

        Register dump

        R0 = 00000400  R1 = 00000009  R2 = 0081C8E7  R3 = 0081C8DF
        R4 = 00000000  R5 = 00000000  R6 = 0081C8EF  R7 = 00000000
        R8 = 000008B4  R9 = 00000008  R10= 000170BA  R11= 000005CC
        AP = 7FE1C214  FP = 7FE1C1D4  SP = 7FE1C250  PC = 00017361
        PSL= 03C00004

%SLS-I-FINISHED, finished volume M00551 on drive _$1$MUA2: at 17-FEB-1997 22:24:11.23
%SLS-I-HSTBUFFS, 2 history block buffers used
$       WRITE SYS$OUTPUT -
"******* End subprocess output for FILES_5 *******"
******* End subprocess output for FILES_5 *******
T.RTitleUserPersonal
Name
DateLines
2200.1COOKIE::MCCLELLANDMarty, SLS/MDMS EngineeringMon Mar 31 1997 14:085
    
    This problem has been reported to engineering as IPMT
    case CFS.49938.  It is under investigation.
    
    	-Marty.
2200.2solution..COOKIE::MCCLELLANDMarty, SLS/MDMS EngineeringThu Apr 03 1997 15:4317
Solution: 

	This ACCVIO is occurring in the VMSBUXX-V55.EXE image which is
        equivalent to the V5.5-2 VMS Backup image V5.5-2R/CI7.1.  This is
        a known problem described in "VAXBACK05_U2055 VAX V5.5-2 - V5.5-2HF 
        BACKUP ECO Summary":

        o  Primarily with unattended SLS BACKUPs and TA90s, an ACCVIO may occur
           immediately after the first tape volume switch when a saveset starts
           in the EOT region of the previous tap volume.  Failure is very
           intermittent.  This problem is fixed in OpenVMS VAX V6.1.