System Administration Commands fsckudfs(1M)
NAME
fsckudfs - file system consistency check and interactive
repair
SYNOPSIS
fsck -F udfs [genericoptions] [special ...]
fsck -F udfs [genericoptions] [-o specificoptions]
[special ...]
DESCRIPTION
fsck audits and interactively repairs inconsistent condi-
tions on file systems. A file system to be checked can be
specified by giving the name of the block or character spe-
cial device or by giving the name of its mount point if a
matching entry exists in /etc/vfstab.
special represents the character special device, for exam-
ple, /dev/rdsk/c0t2d0s0, on which the file system resides.
The character special device, not the block special device
should be used. fsck does not work on a mounted block dev-
ice.
If no special device is specified, all udfs file systems
specified in the vfstab file with a fsckdev entry are
checked. If the -p (preen) option is specified, udfs file
systems with an fsckpass number greater than 1 are checked
in parallel. See fsck(1M).
In the case of correcting serious inconsistencies, by
default, fsck asks for confirmation before making a repair
and waits for the operator to respond with either yes or no.
If the operator does not have write permission on the file
system, fsck defaults to the -n (no corrections) option. See
fsck(1M).
Repairing some file system inconsistencies can result in
loss of data. The amount and severity of data loss can be
determined from the diagnostic output.
fsck automatically corrects innocuous inconsistencies. It
displays a message for each corrected inconsistency that
identifies the nature of the correction which took place on
the file system. After successfully correcting a file sys-
tem, fsck prints the number of files on that file system and
SunOS 5.11 Last change: 5 September 2000 1
System Administration Commands fsckudfs(1M)
the number of used and free blocks.
Inconsistencies checked are as follows:
o Blocks claimed by more than one file or the free
list
o Blocks claimed by a file or the free list outside
the range of the file system
o Incorrect link counts in file entries
o Incorrect directory sizes
o Bad file entry format
o Blocks not accounted for anywhere
o Directory checks, file pointing to unallocated file
entry and absence of a parent directory entry
o Descriptor checks, more blocks for files than there
are in the file system
o Bad free block list format
o Total free block count incorrect
OPTIONS
The following options are supported:
genericoptions The following genericoptions are
supported:
-m Check but do not repair.
This option checks to be
sure that the file system
is suitable for mounting,
and returns the appropri-
ate exit status. If the
file system is ready for
mounting, fsck displays a
message such as:
udfs fsck: sanity check: /dev/rdsk/c0t2d0s0 okay
-n -N Assume a no response to
all questions asked by
SunOS 5.11 Last change: 5 September 2000 2
System Administration Commands fsckudfs(1M)
fsck; do not open the file
system for writing.
-V Echo the expanded command
line, but do not execute
the command. This option
can be used to verify and
to validate the command
line.
-y -Y Assume a yes response to
all questions asked by
fsck.
-o specificoptions Specify udfs file system specific
options in a comma-separated list
with no intervening spaces. The fol-
lowing specificoptions are avail-
able:
f Force checking of file systems
regardless of the state of their
logical volume integrity state.
p Check and fix the file system
non-interactively (preen). Exit
immediately if there is a prob-
lem that requires intervention.
This option is required to
enable parallel file system
checking.
w Check writable file systems
only.
FILES
/etc/vtstab List of default parameters for each file sys-
tem.
ATRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
SunOS 5.11 Last change: 5 September 2000 3
System Administration Commands fsckudfs(1M)
ATRIBUTE TYPE ATRIBUTE VALUE
Availability SUNWudf
SEE ALSO
fsck(1M), fsdbudfs(1M), fstyp(1M), mkfs(1M), mkfsudfs(1M),
mountall(1M), reboot(1M), vfstab(4), attributes(5)
WARNINGS
The operating system buffers file system data. Running fsck
on a mounted file system can cause the operating system's
buffers to become out of date with respect to the disk. For
this reason, use fsck only when the file system is
unmounted. If this is not possible, take care that the sys-
tem is quiescent and that it is rebooted immediately after
running fsck. A panic will probably occur if running fsck on
a file system that modifies the file system while it is
mounted.
If an unmount of the file system is not done before the sys-
tem is shut down, the file system might become corrupted. In
this case, a file system check needs to be completed before
the next mount operation.
DIAGNOSTICS
not writable
You cannot write to the device.
Currently Mounted on
The device is already mounted and cannot run fsck.
FILE SYSTEM WAS MODIFIED
File system has been modified to bring it to a con-
sistent state.
Can't read allocation extent
Cannot read the block containing allocation extent.
Bad tag on alloc extent
SunOS 5.11 Last change: 5 September 2000 4
System Administration Commands fsckudfs(1M)
Invalid tag detected when expecting an allocation
extent.
Volume sequence tag error
Invalid tag detected in the volume sequence.
Space bitmap tag error
Invalid tag detected in the space bitmap.
UNEXPECTED INCONSISTENCY; RUN fsck MANUALY
Use fsck in interactive mode.
SunOS 5.11 Last change: 5 September 2000 5
|
