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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

636.0. "backup v6.2 crash access violation" by IJSAPL::KNOL (isn't every bug a bit wrong) Fri May 23 1997 09:36

    
    
    Openvms vax V6.2 + all patches
    
    
    A customer skips at startup  the rebuild (moun/norebuild) to save
    some time at boot ???.
    When he does a backup of the disk it fails with the following error:
    Is this error because the diskstructure was not correct or is this a bug?
    jan
    
    
    $ BACKUP/IGNORE=INTER/BLOCK=32256/LABEL=(TK0026,TK0083)/FAST -
                DISK$DISK19:[*...]/SINCE=BACKUP
    TZ887:0000048279/SAVE/MEDIA=COMPACT 
    %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual
    address=00000024,
    			PC=00013AA2, PSL=03C00004
    
      Improperly handled condition, image exit forced.
    
    	Signal arguments	      Stack contents
    
    	Number = 00000005		 7FE4B050
    	Name   = 0000000C		 00000000
    		 00000004		 00000000
    		 00000024		 00000000
    		 00013AA2		 00000001
    		 03C00004		 00000000
    					 00000000
    					 00000000
    					 00000000
    					 00000000
    
    	Register dump
    
    	R0 = 00000000  R1 = 0000020E  R2 = 7FE4AF88  R3 = 7FE4B050
    	R4 = 7FE4B050  R5 = 00000000  R6 = 00000001  R7 = 00000000
    	R8 = 00000000  R9 = 00000001  R10= 00000000  R11= 0000402C
    	AP = 7FE4A978  FP = 7FE4A938  SP = 7FE4A9B4  PC = 00013AA2
    	PSL= 03C00004
    
    
    
    
    Sometimes after a ana/disk/repair the backup continues without an error
    
    here follows part of the ana/disk output:
    
    $ ANAL/DISK DISK$DISK19
    Analyze/Disk_Structure for _$1$DIA5: started on 23-MAY-1997 09:28:37.47
    
    %ANALDISK-W-BADHEADER, file (2270,5356,1) 
    	invalid file header
    -ANALDISK-I-HEADER_DEL, deleted file header
    -ANALDISK-I-DELHEADER_BUSY, deleted file header marked "busy"
    	in index file bitmap
    %ANALDISK-W-BADHEADER, file (2342,2249,1) 
    	invalid file header
    -ANALDISK-I-HEADER_DEL, deleted file header
    -ANALDISK-I-DELHEADER_BUSY, deleted file header marked "busy"
    	in index file bitmap
    %ANALDISK-W-BADHEADER, file (2359,1198,1) 
    	invalid file header
    -ANALDISK-I-HEADER_DEL, deleted file header
    -ANALDISK-I-DELHEADER_BUSY, deleted file header marked "busy"
    	in index file bitmap
    %ANALDISK-W-DELHEADER, file (3670,1335,1) CONFIG_DATA.EXE;21
    	marked for delete
    %ANALDISK-W-BADHEADER, file (3678,1258,1) 
    	invalid file header
    -ANALDISK-I-HEADER_DEL, deleted file header
    -ANALDISK-I-DELHEADER_BUSY, deleted file header marked "busy"
    	in index file bitmap
    
    	.
    	.
    	.
    
    %ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated
    	LBN 9404 to 9407, RVN 1
    %ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated
    	LBN 42148 to 42151, RVN 1
    %ANALDISK-W-ALLOCCLR, blocks incorrectly marked allocated
    	LBN 42780 to 42783, RVN 1
    
    	.
    	.
    	.
    
    %ANALDISK-W-INCQUOTA, QUOTA.SYS indicates 842866 blocks used,
    	actual use is 818645 blocks for [SYSTEM]
    %ANALDISK-W-INCQUOTA, QUOTA.SYS indicates 373779 blocks used,
    	actual use is 424332 blocks for [PMDF]
    %ANALDISK-W-INCQUOTA, QUOTA.SYS indicates 82 blocks used,
    	actual use is 90 blocks for [DUP,VDHEIJDEN]
    
    	.
    	.
    	.
    
    %ANALDISK-W-FREESPADRIFT, free block count of 2277048 is incorrect (RVN
    1);
    	the correct value is 2369436
    $
    
    jan
T.RTitleUserPersonal
Name
DateLines
636.1Check the Quotas; QAR/IPMT the ACCVIOXDELTA::HOFFMANSteve, OpenVMS EngineeringFri May 23 1997 10:257
  Take a look at the support database or the documentation set for the
  supported process quota settings -- BACKUP has been known to fall
  over if the quota settings are not as documented.  (This is a bug
  in BACKUP.)

  As for the access violation error reported, QAR (or IPMT) it.