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

Managing Filesets
Open System Services Management and Operations Guide—527191-002
5-30
Inconsistencies Checked by FSCK
Orphan ZYQ
file (continued)
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.
Corrupt record Serious 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.
Bad parent list Serious Each inode contains a list of its parent inode numbers. A
parent list is missing inode numbers or contains incorrect
inode numbers.
Any errors in the list are corrected so that the parent list
accurately reflects the actual links to the inode.
Missing ZYQ
file
Minor The ZYQ file corresponding to a regular inode does not exist.
Because this inconsistency is usually the result of a failure
during file creation or during the removal of the last link to a
file, the inode and any links to it are deleted.
Wrong fileset
type
Serious 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 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.
Table 5-2. Inconsistencies Checked by FSCK (page3of4)
Inconsistency Type Explanation