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

Table 11 Inconsistencies Checked by FSCK (continued)
ExplanationTypeInconsistency
There is a ZYQ file for which there is no inode.If the ZYQ file is
empty, FSCK issues a warning message and purges the file. If the
MinorOrphan ZYQ file
file is nonempty, FSCK obtains the current number of links for the
file from the disk process.If the number of links is zero and the file
is not currently open, FSCK purges the file. If the link count is
nonzero, FSCK does the following:
1. An inode is allocated for the file.
2. The disk process copy of the link count is set to one.
3. The file is placed in /lost+found under a synthesized OSS
filename.
FSCK attempts to use the inode whose number is encoded in the
name of the ZYQ file. If that inode is unavailable, FSCK allocates
an unused inode and renames the ZYQ file so that its name reflects
this new inode number. If the ZYQ file cannot be renamed, a
warning is issued and the new inode is not added.
Records containing undefined record types or with record lengths
inappropriate for the type of record are deleted. This applies to
records in both the PXLINK and PXINODE files.
SeriousCorrupt record
Each inode contains a list of its parent inode numbers. A parent
list is missing inode numbers or contains incorrect inode
SeriousBad parent list
numbers.Any errors in the list are corrected so that the parent list
accurately reflects the actual links to the inode.
The ZYQ file corresponding to a regular inode does not exist.
Because this inconsistency is usually the result of a failure during
MinorMissing ZYQ file
file creation or during the removal of the last link to a file, the
inode and any links to it are deleted.
The root fileset on a system is unique in that it contains special
files not required in other filesets (such as /E and /G). Normally
SeriousWrong fileset type
the root fileset is assigned fileset identifier (device number) 0 and
its catalog resides in a subvolume named ZX000000. Recorded
in the first record (superblock) of the PXINODE catalog is the fileset
type (root or nonroot).If the catalog subvolume is ZX000000,
FSCK assumes that it is operating with a root fileset. When dealing
with a root fileset, FSCK makes additional checks regarding the
existence and integrity of special files (/E, /G, /dev, /dev/tty,
and /dev/null).If the subvolume name or the keyword indicates
a root fileset but the catalog indicates otherwise, FSCK reports
numerous inconsistencies and converts the catalog into a root
catalog. If the subvolume name is other than ZX000000 but the
superblock indicates that it corresponds to a root fileset, FSCK
issues a warning message and does not perform those checks or
repairs that are unique to root filesets.
A record in the PXINODE file has an inode number that is one of
the following cases:
Serious or minorInvalid inode number
• Less than or equal to 0 (zero)
• Greater than or equal to 2
31
• In the reserved inode range 8 through 31
If the inode number is <=0 or >= 2
31
, the inode is discarded
along with any links to the inode. These cases are serious
inconsistencies.If the inode number is in the reserved inode range,
the inode is relocated to a currently unused inode number and
the PXLINK records for the inode are adjusted accordingly. If the
inode represents a regular file, the ZYQ file is renamed to reflect
the new inode number. This case is a minor inconsistency.If FSCK
fails after renaming a ZYQ file but before the new catalog is
completely created, then the next time FSCK is run against the old
164 Managing Filesets