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

If the DETAIL option is also used, the mounted field contents are displayed in hexadecimal. Possible
values are:
Mounted stateValue
The fileset is unmounted.0x0000
The fileset is being recovered.0x0001
The fileset is mounted in BUFFERED LOG mode by an OSS name server that is not running the
current code version.
0x0002
The fileset is mounted in BUFFERED CREATE mode by an OSS name server that is not running the
current code version.
0x0006
The fileset is mounted in BUFFERED CREATE mode.0x2004
The fileset is mounted in READONLY TRUE mode.0x2010
The fileset is mounted in BUFFERED LOG mode and is marked clean.0x6002
The fileset is being recovered.0x8001
The fileset is mounted in BUFFERED LOG mode.0x8002
The fileset is mounted in BUFFERED NONE mode.0xA000
The fileset is mounted in BUFFERED NONE mode by an OSS name server that is not running the
current code version.
0xFFFF
When the mounted field does not correspond to a known state, FSCK reports its hexadecimal value
as follows:
The fileset is in Mount State = 0xvalue
For information about messages such as the following, see “Messages” (page 335):
*** SERIOUS 201 *** Broken Free List, Inode=5465
Inconsistencies Checked by FSCK
The FSCK utility checks for the inconsistencies listed in Table 11. The inconsistencies are listed in
the order in which FSCK checks them. The corresponding FSCK log file messages are described
in “Messages” (page 335).
Table 11 Inconsistencies Checked by FSCK
ExplanationTypeInconsistency
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.
SeriousMissing or corrupt superblock
Each time a fileset is mounted for read/write access, its mounted
flag is set to a nonzero value. When the fileset is successfully
MinorNonzero mounted flag
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
162 Managing Filesets