pSOSystem System Calls - Read

pHILE+ System Calls verify_vol
Usage
Hex Mnemonic Description
0x200A E_DMOUNT Volume not mounted.
0x2021 E_ILLDEV Illegal device (exceeded maximum).
0x2025 E_IDN Illegal device name.
0x2051 E_MAXLOOP Symbolic links nested too deeply.
0x2200 VF_INSUFF Insufficient working area provided.
0x2201 VF_MAXDEPTH Maximum depth exceeded on
directory traversal.
0x2202 VF_ABORT Verify routine aborted by user.
verify_vol() can be used to perform the following actions:
Volume Integrity Verification — verify_vol() examines all volume control structures to
verify their consistency. Inconsistencies are reported and described in detail.
Volume Correction — Certain kinds of inconsistencies can be corrected.
Bad Block Elimination — Bad blocks can be marked as “in use” in the volume bitmap,
thus excluding them from allocation by pHILE+ file system manager.
verify_vol() can be used in two ways. First, it can be used to perform a simple
test of correctness, for example, at each power-on or system restart. Second, it can
be integrated into a volume repair utility with a user-supplied interface.
Under normal operating conditions, pHILE+ file system manager always maintains
the volume control structures in a correct and consistent state. verify_vol() is
most useful when used following a system error or failure that can corrupt the file
system, such as one of the following:
■ A power failure, or a CPU or disk controller crash. In such cases, pHILE+ file
system manager can be interrupted in the middle of a critical operation,
resulting in a corrupted file system.
■ A hard error or data corruption in one or more blocks containing volume control
structures.
■ Errors in the user-supplied physical disk driver.
■ Restarting a task in pHILE+ file system manager.
pSOSystem System Calls 2-129
2