Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Filesets
Open System Services Management and Operations Guide527191-002
5-28
Inconsistencies Checked by FSCK
Table 5-2. Inconsistencies Checked by FSCK (page1of4)
Inconsistency Type Explanation
Missing or
corrupt
superblock
Serious If the superblock (node #1) is missing from the PXINODE file,
the fileset is unusable. A new superblock must be constructed.
FSCK creates the new superblock; you do not need to do
anything.
Nonzero
mounted flag
Minor Each time a fileset is mounted for read/write access, its
mounted flag is set to a nonzero value. When the fileset is
successfully unmounted, the mounted flag is set to zero.
A nonzero mounted flag means that the fileset has not been
cleanly unmounted because one of the following is true:
The OSS name server on which the fileset was mounted
failed.
The OSS name server detected serious inconsistencies
within the catalog.
Although a nonzero mounted flag is a minor inconsistency, it is
corrected regardless of whether FSCK has been directed to
correct minor inconsistencies.
If only minor inconsistencies are discovered and only major
inconsistencies are being corrected, FSCK does not create a
Bad free-inode
list
Serious An OSS name server maintains two free-inode lists in each
catalog. One is used to list the inodes that can be immediately
reused. The other is used to list those inodes that can be
reused only after a successful unmount and mount sequence.
The FSCK utility detects and corrects the following
inconsistencies:
An inode other than a free-inode block appears on a free-
inode list.
A loop occurs in a free-inode list.
An in-use inode also appears in a free-inode block.
The same free-inode block appears on both free-inode
lists.
If any free-inode list inconsistencies are found, the free-inode
lists are rebuilt.
If FSCK is run using the SCF DIAGNOSE FILESET command,
FSCK places all free inodes in the list of inodes that can be
reused immediately.
If FSCK is run automatically by the OSS Monitor as a result of
a failure of an OSS name server, FSCK places all free inodes
in the list of inodes that cannot be reused until after an
unmount and remount sequence.