Open System Services Management and Operations Guide (G06.29+, H06.07+)

Messages
Open System Services Management and Operations Guide—527191-005
A-25
FSCK Inconsistency and Error Messages
304
filename
indicates the affected file.
Cause. The indicated Guardian disk file is either an empty orphan ZYQ file or a file
belonging to an incomplete catalog left behind when an earlier execution of FSCK was
interrupted.
Effect. The indicated file is purged and FSCK proceeds with its checking.
Recovery. Informational message only; no corrective action is needed.
305
Cause. The indicated file was not a valid OSS fileset catalog file. It had an incorrect
file type, file code, or key structure.
Effect. The FSCK utility terminates abnormally.
Recovery. Check for a typographical error in the volume, subvolume, or file identifier
of the filename for the correct file. Remove the invalid file, rename the appropriate
PXINnnnn, PXLInnnn, or PXLOnnnn file if needed, and reissue the command.
306
Cause. To improve performance, FSCK uses buffered access to the new catalog files,
then uses the Guardian SETMODE 95 operation to flush any dirty cache blocks to disk.
The SETMODE 95 operation returned an indication that one of the new files has its
broken-file flag on because of a disk write error.
Effect. The FSCK utility terminates abnormally.
Recovery. Determine the cause of the disk write failure, correct it, then reissue the
command.
WARNING 304 - filename Purged
ERROR 305 - Invalid { PXINODE | PXLOG | PXLINK } File
ERROR 306 - DP2 Cache Flush Write Error