Conference cookie::archive_backup

468.0. "abs$ubs crash abs v2.1" by IJSAPL::KNOL (isn't every bug a bit wrong) Fri May 23 1997 03:56

    problem abs$ubs is crashing.... known problem?
    
    
Executing ABS LOGIN.COM
Completed execution of ABS LOGIN.COM
"@abs_system:coordinator.com 4840C319-BC98-11D0-A818-08002B398C07" Executing, output follows :
------------------------------------------------------
---------------------------------------------------------------
Starting New Request at 22-MAY-1997 19:00:26.99
   Name:   SATURNUS_FULL_SAVE
   UID:    4840C319-BC98-11D0-A818-08002B398C07   

COORDINATOR:  Created new volume set: AAK295
COORDINATOR:  Mounting volume set member: AAK295 RVN 1
COORDINATOR:     (Selected drive $1$MUA11:)
COORDINATOR:  Initializing scratch volume AAK295
%MOUNT-I-MOUNTED, AAK295 mounted on _$1$MUA11: (HSJ010)
COORDINATOR:  Skipping $1$MUA11: to End of Tape...
THREAD #1:   

Operation #1 starting at 22-MAY-1997 19:03:02.90

   Data Movement Type:    FULL_SAVE
   Incremental Level:     Full Operation

   Object Set:
      Object Type:        UNIX Files gtar
      Include List:       /usr/*
      Exclude List:       

   Archive Information:
      Storage Class Name: UNIX_BACKUPS
      Saveset Location:   AAK295
      Saveset Name:       22MAY19971900270.

   Execution Environment:
      Name:               UNIX_BACKUPS_ENV
      Number of retries:  0
      Retry Interval:     0 minute(s)


THREAD #1:  $  
THREAD #1:  SET NOON 
THREAD #1:  $ DEFINE SYS$COMMAND sys$input: 
THREAD #1:  $ ubs := $ABS$SYSTEM:ABS$UBS.EXE  
THREAD #1:  $ ubs n?SATURNUS u?"root" l?_MBA224: - 
THREAD #1:  _$ "d?$1$MUA11:22MAY19971900270." - 
THREAD #1:  _$ af?SL 
THREAD #1:  S os?"UNIX"  s - 
THREAD #1:  _$ "c?ABSgtar -cvPGpb20 --totals --same-owner   -f - -N @1970-1-2@ /usr/*"   
THREAD #1:  %ABS-I-STARTED, ubs agent is started 
THREAD #1:  Total bytes written: 369694720%%Status 0 
THREAD #1:  %ABS --UBS SUCCESS-- Gtar status may vary 
THREAD #1:  $  
THREAD #1:  Normal successful completion 
COORDINATOR:  Skipping $1$MUA11: to End of Tape...
THREAD #1:   
THREAD #2:   

Operation #2 starting at 22-MAY-1997 19:10:44.91

   Data Movement Type:    FULL_SAVE
   Incremental Level:     Full Operation

   Object Set:
      Object Type:        UNIX Files gtar
      Include List:       /sapmnt/VGD
      Exclude List:       

   Archive Information:
      Storage Class Name: UNIX_BACKUPS
      Saveset Location:   AAK295
      Saveset Name:       22MAY19971910398.

   Execution Environment:
      Name:               UNIX_BACKUPS_ENV
      Number of retries:  0
      Retry Interval:     0 minute(s)


THREAD #2:  $  
THREAD #2:  SET NOON 
THREAD #2:  $ DEFINE SYS$COMMAND sys$input: 
THREAD #2:  $ ubs := $ABS$SYSTEM:ABS$UBS.EXE  
THREAD #2:  $ ubs n?SATURNUS u?"root" l?_MBA620: - 
THREAD #2:  _$ "d?$1$MUA11:22MAY19971910398." - 
THREAD #2:  _$ af?SL 
THREAD #2:  S os?"UNIX"  s - 
THREAD #2:  _$ "c?ABSgtar -cvPGpb20 --totals --same-owner   -f - -N @1970-1-2@ /sapmnt/VGD"   
THREAD #2:  %ABS-I-STARTED, ubs agent is started 
THREAD #2:  Total bytes written: 197447680%%Status 0 
THREAD #2:  %ABS --UBS SUCCESS-- Gtar status may vary 
THREAD #2:  $  
THREAD #2:  Normal successful completion 
COORDINATOR:  Skipping $1$MUA11: to End of Tape...
THREAD #3:   

Operation #3 starting at 22-MAY-1997 19:13:46.84

   Data Movement Type:    FULL_SAVE
   Incremental Level:     Full Operation

   Object Set:
      Object Type:        UNIX Files gtar
      Include List:       /oracle/VGD
      Exclude List:       

   Archive Information:
      Storage Class Name: UNIX_BACKUPS
      Saveset Location:   AAK295
      Saveset Name:       22MAY19971913419.

   Execution Environment:
      Name:               UNIX_BACKUPS_ENV
      Number of retries:  0
      Retry Interval:     0 minute(s)


THREAD #3:  $  
THREAD #2:   
THREAD #3:  SET NOON 
THREAD #3:  $ DEFINE SYS$COMMAND sys$input: 
THREAD #3:  $ ubs := $ABS$SYSTEM:ABS$UBS.EXE  
THREAD #3:  $ ubs n?SATURNUS u?"root" l?_MBA794: - 
THREAD #3:  _$ "d?$1$MUA11:22MAY19971913419." - 
THREAD #3:  _$ af?SL 
THREAD #3:  S os?"UNIX"  s - 
THREAD #3:  _$ "c?ABSgtar -cvPGpb20 --totals --same-owner   -f - -N @1970-1-2@ 
    /oracle/VGD"   
THREAD #3:  %ABS-I-STARTED, ubs agent is started 
THREAD #3:  Total bytes written: -552982528%%Status 0 
THREAD #3:  assert error: expression = section_block_count <= 999999, in file 
    RESD$:[SRC]VMSTAPE.CXX;1 at line 2679 
THREAD #3:  %SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=8059555C, 
    PS=0000001B 
THREAD #3:    Improperly handled condition, image exit forced. 
THREAD #3:      Signal arguments:   Number = 00000003 
THREAD #3:                          Name   = 00000434 
THREAD #3:                                   8059555C 
THREAD #3:                                   0000001B 
THREAD #3:      Register dump: 
THREAD #3:      R0  = 0000000000000001  R1  = 0000000000000001  R2  = 
    000000007F397E80 
THREAD #3:      R3  = FFFFFFFFFFFFFFFE  R4  = 0000000000000434  R5  = 
    0000000000000001 
THREAD #3:      R6  = 0000000000000006  R7  = 00000000007991E8  R8  = 
    0000000000000002 
THREAD #3:      R9  = 0000000000000000  R10 = 0000000000000001  R11 = 
    0000000000026F80 
THREAD #3:      R12 = 000000007EDA1B58  R13 = 00000000000248B0  R14 = 
    0000000000000000 
THREAD #3:      R15 = 000000007EE59DA0  R16 = 0000000000000434  R17 = 
    0000000000000000 
THREAD #3:      R18 = 0000000000000001  R19 = 00000000F0000000  R20 = 
    0000000030000000 
THREAD #3:      R21 = 000000000000004A  R22 = 00000000006EF9B4  R23 = 
    0000000000000000 
THREAD #3:      R24 = 00000000009F78D0  R25 = 0000000000000001  R26 = 
    FFFFFFFF8059555C 
THREAD #3:      R27 = 000000007F02AB20  R28 = 300000000000001B  R29 = 
    000000007EDA17B0 
THREAD #3:      SP  = 000000007EDA17B0  PC  = FFFFFFFF8059555C  PS  = 
    300000000000001B 
THREAD #3:  $  
THREAD #3:  Normal successful completion 
COORDINATOR:  Skipping $1$MUA11: to End of Tape...
COORDINATOR:  Dismounting volume set member: AAK295 RVN 1
COORDINATOR:  Failed to access Storage Class
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Failed to access Storage Class
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 1309, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 801, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 704, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 469, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 1717, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 4819, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 540, File = RESD$:[SRC]TAPE_OPERATIONS.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-F-PARITY, parity error
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000020, 
    PC=005E70D4, PS=0000001B
Exception                          Module                                   Line
Exception Reraised by:             COORDINATOR                               995
exception                          COORDINATOR                               908
COORDINATOR:  Final status is Unexpected exception in Coordinator
%SYSTEM-F-OPINCOMPL, operation is incomplete
  ABS          job terminated at 22-MAY-1997 22:33:42.44

  Accounting information:
  Buffered I/O count:            4140         Peak working set size:  14560
  Direct I/O count:              1444         Peak page file size:    71872
  Page faults:                   1822         Mounted volumes:            1
  Charged CPU time:           0 00:00:07.64   Elapsed time:     0 03:33:42.42
    

    
    Jan,
    
    I have not seen this problem personally.  I have to see if other people 
    from the team has seen this.  The problem is that we have 3 day weekend
    (5/24-26) in U.S. and lots of people are either on vacataion or left
    early for the holiday.  
    
    We'll get back to you early next week.
    
    Masami

Not one of the engineers but that parity error looks suspicious.  You may want
to try a new tape or cleaning the tape drive.  Just a thought...

Ted

.0 states that ABS$UBS is crashing...
Does this imply that this has happened more than once? Or
was this an isolated instance?  Can it be reproduced with
the same device and tape?

The parity error may indicate a problem with the tape or
drive but not necessarily, we may have ignored the end of
tape indicator and when the system attempted to write the
end of volume marks it encountered a portion of the tape
that was not writable.

The save that failed, /oracle/VGD appears to have completed
successfully, but the number of bytes reported appears to
have overflowed the signed long storing the information.
Can you find out how many bytes of data are actually in the
directory structure?

Thanks,
Lyle