fsck(1M-vxfs) (VxFS) fsck(1M-vxfs)
NAME
fsck (vxfs) - check and repair a Veritas File System (VxFS)
SYNOPSIS
fsck [-F vxfs] [genericoptions] [-o full,nolog] special ...
DESCRIPTION
This manual page is an addendum to the fsck(1M) manual page. It
describes the Veritas File System (VxFS) specific features of the fsck
command.
When VxFS is installed on the system, the following additional options
are available:
-F vxfs Specifies the Veritas file system type (FSType).
genericoptions
Options supported by the generic fsck command.
-o Specifies Veritas-specific options. These options can be a
combination of the following in a comma-separated list:
full Performs a full file system check. The default is to
perform an activity log replay only. Since the Veritas
file system maintains an activity log, a complete
check is generally not required. If the file system
detects damage or the log replay operation detects
damage, an indication that a complete check is
required is placed in the super block, and a full
check is performed.
nolog Do not perform log replay. This option may be used if
the log area was physically damaged.
When a full check is performed, the following inconsistencies are
checked:
1. Blocks claimed by more than one inode or the free list.
2. Blocks claimed by an inode outside the range of the file system.
3. Incorrect link counts.
4. Size checks:
Incorrect number of blocks.
Directory entry format.
5. Bad inode format.
6. Blocks not accounted for anywhere.
Page 1 Reliant UNIX 5.44 Printed 11/98
fsck(1M-vxfs) (VxFS) fsck(1M-vxfs)
7. Directory checks:
File pointing to unallocated inode.
Inode number out of range.
Linkage to parent directory.
Hash chain linkage.
Free space count.
8. Super block checks:
Checksum mismatch.
More blocks for inodes than there are in the file system.
9. Bad free block list format.
10. Total free block and/or free inode count incorrect.
Orphaned files and directories (allocated but unreferenced) are, with
the user's concurrence, reconnected by placing them in the lost+found
directory. The name assigned is the inode number. The only restriction
is that the directory lost+found must already exist in the root of the
file system being checked.
OUTPUT
Structural errors discovered during a full check are displayed on
stdout. Responses required during a full check are read from stdin.
The following return codes are used for the -m (generic) option for
all devices other than the one used by the root file system:
0 The file system is unmounted and clean.
32 The file system is unmounted and needs checking.
33 The file system is mounted.
34 The stat of the device failed.
Other The state could not be determined because of an error.
The following return codes are used for the -m (generic) option for
the device used by the root file system:
0 The root file system is mounted read-only and is clean, or the
root file system is mounted read/write and therefore, does not
need checking.
32 The root file system is mounted read-only and needs checking.
34 The stat of the device failed.
Other The state could not be determined because of an error.
Page 2 Reliant UNIX 5.44 Printed 11/98
fsck(1M-vxfs) (VxFS) fsck(1M-vxfs)
ERROR/DIAGNOSTICS
All error messages that relate to the contents of a file system pro-
duced during a log replay are displayed on stdout. All I/O failures
and exit messages are displayed on stderr.
NOTES
A full file system check will always perform any pending extended
inode operations without operator interaction. If a structural flaw is
detected, the full fsck flag will be set on the file system, without
operator interaction.
SEE ALSO
crash(1M), fsck(1M), mkfs(1M), ncheck(1M), uadmin(2), fs(4-vxfs).
Page 3 Reliant UNIX 5.44 Printed 11/98