ODFU V3.0 !

DFU V3.0


1Previous. | Contents


'VERIFY can report the following errors:

.ALLOCCLR, blocks incorrectly marked allocated,

Severity: ERROR
HExplanation: Blocks were found which are not allocated Dby a file but set in the BITMAP file. This error is often seen when GVERIFY is run and there is concurrent file activity on the disk. Also, Hif after a system crash the disk is mounted with /NOREBUILD such blocks Fmay exist. ReRun VERIFY with /LOCK to see if the error is still there.
GUser Action: Run VERIFY/REBUILD to rebuild the BITMAP file.
)ALLOCSET, blocks incorrectly marked free,

Severity: ERROR
GExplanation: Blocks were found which are allocated by Ea file but not set in the BITMAP file. This error is often seen when GVERIFY is run and there is concurrent file activity on the disk. Also, Hif after a system crash the disk is mounted with /NOREBUILD such blocks Fmay exist. ReRun VERIFY with /LOCK to see if the error is still there.
GUser Action: Run VERIFY/REBUILD to rebuild the BITMAP file.
(BADBLOCK, file has suspected bad blocks,

Severity: ERROR
GExplanation: A file has suspected bad blocks. This is 3likely to be caused by hardware errors on the disk.
HUser Action: Try to copy the file to another location. Also check the Error Log.
+BADEXTLNK, link to extension header broken,

Severity: ERROR
HExplanation: VERIFY tries to follow the extension link >of the file and it failed, or the extension header is invalid.
EUser Action: Try ANALYZE/DISK/REPAIR. However, this Gmay be an unrepairable error, in which case the file will be corrupted and unreliable.
9BADMFDLNK, directory has backlink to 000000.DIR on RVN n,

Severity: ERROR
EExplanation: A directory has a backlink to a Master Gfile directory other than the one on RVN 1. This is incorrect, but the Bonly way to recover is to reenter the directory manually into the 000000.DIR on RVN 1.
FUser Action: Do a SET FILE/ENTER into the 000000.DIR Hdirectory on RVN 1, then do a SET FILE/REMOVE from the wrong 000000.DIR.
DELETED, file marked for delete,

"Severity: WARNING
DExplanation: A file was found marked for deletion. ESuch files usually exists as a result of file being deleted while it Awas still INSTALLed, or as a result of a system crash. It is not Econsidered as an error. VERIFY/FIX may be able to cleanup such files.
ERRHOME, Home block info not OK,

Severity: ERROR
GExplanation: The Info contained in the Home Block was not consistent or corrupted.
HUser Action: Run ANALYZE/DISK/REPAIR to try to fix the error.
%INVBAKFID, file has invalid backlink,

Severity: ERROR
GExplanation: The files backlink file id is not filled Ein. This is likely to be a lost file. (Note that once VERIFY reports Fthis error, it will not be reported again during the LOSTFILE check). EBut is also possible that the file is in a valid directory, but that &the Backlink file id is not filled in.
FUser Action: Run ANALYZE/DISK/REPAIR. If the file is Gin a valid directory the backlink will be repaired. Otherwise the file )will be moved to the [SYSLOST] directory.
)LINKCOUNT, linkcount set to n, must be m,

"Severity: WARNING
FExplanation: This error indicates that DFU has found Bfiles, for which the linkcount does not match the number of found Gdirectory entries for this file. This error will only be reported on a Edisk with hardlinks enabled, and only when using the /DIRECTORY_SCAN qualifier.
?User Action: Run VERIFY/DIR/FIX to repair the linkcount.
LOCKED, file is deaccess locked,

"Severity: WARNING
GExplanation: The file is deaccess locked. This may be a result of a system crash.
FUser Action: Try to unlock the file with the DFU SET #command, or the DCL UNLOCK command.
.LOSTHDR1, file found in nonexistent directory,

"Severity: WARNING
DExplanation: During the lost file check a file was Cdiscovered in a nonexistent directory. This error can be caused as <follows : set a directory file to NODIRECTORY and delete it.
EUser Action: Run VERIFY/FIX to move the file to the [SYSLOST] directory.
4LOSTHDR2, file found in directory with bad backlink,

"Severity: WARNING
DExplanation: During the lost file check a file was Gdiscovered in a valid directory. However, the directory has an invalid Cbacklink. This error can be caused by doing a SET FILE/REMOVE of a directory file.
FUser Action: Run VERIFY/FIX to move the directory to Ethe [SYSLOST] directory. Then move the directory back to the correct ?location. The files in the directory should be accesible again.
*LOSTHDR3, file found in invalid directory,

"Severity: WARNING
DExplanation: During the lost file check a file was Ediscovered in a directory which is not a valid directory. Either the Hfile has a wrong backlink, or the directory file has the directory file attribute not set.
GUser Action: Look up the directory and use DFU SET to Hset the directory bit. If the directory file was OK then run VERIFY/FIX to recover the lost file.
#LOSTHDR4, not found in a directory,

"Severity: WARNING
DExplanation: When the /DIRECTORY_SCAN qualifier is Fused, DFU detects files which have a valid backlink but which are not 6seen in the directory. This can be repaired with /FIX.
GUser Action: Using /FIX will enter these files in the correct directory.
%MULTALLOC, blocks multiple allocated,

Severity: ERROR
HExplanation: A file has blocks allocated which already Abelong to another file. Note that VERIFY will make a second pass Gthrough INDEXF.SYS to report all the files involved. This is a serious Derror, and may be a result of a disk being mounted on two seperated *VAXClusters (or a partitioned VAXCluster).
BUser Action: Copy all the files found to another Dlocation. Next all the files must be deleted. Run VERIFY/REBUILD to Frepair the BITMAP. All the afflicted files must be manually inspected 5to see which files are valid and which are corrupted.
*NOBITCLR, Deleted file header marked BUSY,

"Severity: WARNING
HExplanation: A file was deleted. The corresponding bit Gin the INDEXF bitmap should be cleared but is still set. This is not a serious error.
BUser Action: Run VERIFY/REBUILD to fix the error.
(NOBITSET, index file bitmap bit not set,

"Severity: WARNING
>Explanation: A valid file was found, but the Dcorresponding index file bitmap bit is clear. This is not a serious error.
BUser Action: Run VERIFY/REBUILD to fix the error.
NOOWNER, file has no owner,

"Severity: WARNING
EExplanation: A file was found with UIC [0,0] as the &owner. This is not a normal situation.
CUser Action: Look up the file and modify the file owner.
@QUOTAERR, UIC [x,y] has n blocks used, QUOTA indicates m blocks,

"Severity: WARNING
FExplanation: If a disk has diskquota enabled, VERIFY Ccalculates the blocks used and compares them with the value in the HQUOTA.SYS file. Any mismatch is reported. This error is often seen when HVERIFY is run, and there is concurrent file activity on the disk. Also, Gif after a system crash the disk is mounted with /NOREBUILD such Quota Emismatches may exist. ReRun VERIFY with /LOCK to see if the error is still there.
FUser Action: Run VERIFY/REBUILD to rebuild the QUOTA -file. Or run a DISKQUOTA> REBUILD command.
%SLFBAKFID, backlink points to itself,

"Severity: WARNING
HExplanation: This error indicates that DFU has found a Cdirectory with a backlink pointing to itself. This feature is only Gallowed for the MFD 000000.DIR. This error will result in ANALYZE/DISK going into a COMputable loop.
FUser Action: Run VERIFY/FIX to move the directory to Ethe [SYSLOST] directory. Then remove the directory entry from itself Ewith a SET FILE/REMOVE command. The files in the directory should be accesible again.
'

VERIFY



*VERIFY a device for disk structure errors.



Format



VERIFY device[:]




PARAMETERS



device

The device to be verified.



QUALIFIERS



/APPEND=filename

AThis qualifier redirects the output to be appended to an already Fexisting file. If the output file does not exists it will be created. $Use /APPEND or /OUTPUT but not both.

/DIRECTORY_SCAN

CPerforms a full directory scan. This may take up some time, but it Fallows detection of mismatches between the directories and INDEXF.SYS.

/FIX



/NOFIX (default)

FRepair errors on the disk. File marked for delete will be deleted and 6lost files and directories will be moved to [SYSLOST].

/LOCK



/NOLOCK (default)

ELocks the disk for file allocation/deletion. This gives a consistent Areport for the disk, but other users may experience a delay when Haccessing the disk. The device will be unlocked a the end of the VERIFY command.

/OUTPUT=filename

GThis qualifier redirects the output to a file. The output will also go Hto SYS$OUTPUT. CAUTION: if one uses /LOCK in combination with /OUTPUT , Hbe careful to specify an outputfile on ANOTHER disk, or DFU will finish with a severe error.

/REBUILD



/NOREBUILD (default)

EPerform a volume rebuild. Using this qualifier will temporarily lock the disk for other users.

/STATISTICS

FThis qualifier displays the performance statistics: CPU time, Elapsed Time, I/O and PageFaults.


1Previous. | Contents. | Contents