Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Table 11 Inconsistencies Checked by FSCK (continued)
ExplanationTypeInconsistency
catalog, the ZYQ file is restored to its original name and the
PXINODE file is updated to reflect the new CRVSN of the file.
Generated Catalog Files
The FSCK utility saves a copy of the existing catalog and creates a new one. Each time that FSCK
is run to repair a fileset catalog, a unique four-digit FSCK serial number (FSN) is assigned for that
run.
The FSN is used to encode the names of the saved files as follows:
CodeFile Name
PXINnnnnPXINODE:
PXLInnnnPXLINK:
PXLOnnnnPXLOG:
where nnnn is the FSN.
During the final phase of FSCK, the catalog files are renamed. During this phase, FSCK might fail
or be otherwise stopped when there are no files in the catalog subvolume with the names PXINODE,
PXLINK, or PXLOG. To allow for the orderly restart of FSCK in this case, FSCK creates a file named
PXCKSTAT in the catalog subvolume. The PXCKSTAT file records the current FSN so that FSCK can
locate the most recent catalog files.
After the catalog has been completely repaired (rebuilt), the PXCKSTAT file is purged from the
catalog subvolume. The renamed catalog files remain in the subvolume until you purge or rename
them with the Guardian Catalog Volume Tool (CVT).
For information about the CVT utility, see “Managing and Repairing Fileset Catalog Files” (page 170).
What Happens When Diagnosis Appears to Fail?
Errors occurring on ZYQ files cause FSCK to issue a warning and continue. In these cases, the
new catalog might still contain minor inconsistencies.
Any other errors occurring during writes to the new catalog files cause FSCK to issue an error
message and terminate.
When FSCK restarts a failed run that has renamed ZYQ files, it restores these files and attempts
to update the PXINODE file accordingly. If an I/O error occurs during this update, FSCK issues a
warning and attempts to continue.
The FSCK run might fail if there is a file input or output error. If you place fileset catalogs on mirrored
volumes, you eliminate most I/O errors on catalog files.
If FSCK encounters:
• Any read error on the old catalog other than Guardian File Management Error 1 (reaching
an end of file), it issues an error message and terminates abnormally.
• A Guardian File Management Error 1 (reaching an end of file) on the new PXLINK file, FSCK
issues a warning message and continues.
Any other errors occurring during writes to the new catalog files cause FSCK to issue an error
message and terminate.
• Any error other than Guardian File Management Error 1 (reaching an end of file) on FSCK’s
inode swap file, FSCK issues an error message and terminates.
• An inconsistency in its internal data structures, it issues an error message and terminates.
Checking and Repairing Fileset Integrity 165