2 .\" Copyright (c) 2000 Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH FSCK_UDFS 1M "Nov 26, 2017"
8 fsck_udfs \- file system consistency check and interactive repair
12 \fBfsck\fR \fB-F\fR udfs [\fIgeneric_options\fR] [\fIspecial \|.\|.\|.\fR]
17 \fBfsck\fR \fB-F\fR udfs [\fIgeneric_options\fR] [\fB-o\fR \fIspecific_options\fR]
18 [\fIspecial \|.\|.\|.\fR]
23 \fBfsck\fR audits and interactively repairs inconsistent conditions on file
24 systems. A file system to be checked can be specified by giving the name of the
25 block or character special device or by giving the name of its mount point if a
26 matching entry exists in \fB/etc/vfstab\fR.
29 \fIspecial\fR represents the character special device, for example,
30 \fB/dev/rdsk/c0t2d0s0\fR, on which the file system resides. The character
31 special device, not the block special device should be used. \fBfsck\fR does
32 not work on a mounted block device.
35 If no special device is specified, all \fBudfs\fR file systems specified in the
36 \fBvfstab\fR file with a \fBfsckdev\fR entry are checked. If the \fB-p\fR
37 (\fBpreen\fR) option is specified, \fBudfs\fR file systems with an
38 \fBfsckpass\fR number greater than \fB1\fR are checked in parallel. See
42 In the case of correcting serious inconsistencies, by default, \fBfsck\fR asks
43 for confirmation before making a repair and waits for the operator to respond
44 with either \fByes\fR or \fBno\fR. If the operator does not have write
45 permission on the file system, \fBfsck\fR defaults to the \fB-n\fR (no
46 corrections) option. See \fBfsck\fR(1M).
49 Repairing some file system inconsistencies can result in loss of data. The
50 amount and severity of data loss can be determined from the diagnostic output.
53 \fBfsck\fR automatically corrects innocuous inconsistencies. It displays a
54 message for each corrected inconsistency that identifies the nature of the
55 correction which took place on the file system. After successfully correcting a
56 file system, \fBfsck\fR prints the number of files on that file system and the
57 number of used and free blocks.
60 Inconsistencies checked are as follows:
65 Blocks claimed by more than one file or the free list
71 Blocks claimed by a file or the free list outside the range of the file system
77 Incorrect link counts in file entries
83 Incorrect directory sizes
95 Blocks not accounted for anywhere
101 Directory checks, file pointing to unallocated file entry and absence of a
102 parent directory entry
108 Descriptor checks, more blocks for files than there are in the file system
114 Bad free block list format
120 Total free block count incorrect
124 The following options are supported:
128 \fB\fIgeneric_options\fR\fR
131 The following \fIgeneric_options\fR are supported:
138 Check but do not repair. This option checks to be sure that the file system is
139 suitable for mounting, and returns the appropriate exit status. If the file
140 system is ready for mounting, \fBfsck \fRdisplays a message such as:
144 udfs fsck: sanity check: /dev/rdsk/c0t2d0s0 okay
154 \fB\fB-n\fR | \fB-N\fR\fR
157 Assume a \fBno\fR response to all questions asked by \fBfsck\fR; do not open
158 the file system for writing.
167 Echo the expanded command line, but do not execute the command. This option can
168 be used to verify and to validate the command line.
174 \fB\fB-y\fR | \fB-Y\fR\fR
177 Assume a \fByes\fR response to all questions asked by \fBfsck\fR.
185 \fB\fB-o\fR \fIspecific_options\fR\fR
188 Specify \fBudfs\fR file system specific options in a comma-separated list with
189 no intervening spaces. The following \fIspecific_options\fR are available:
196 Force checking of file systems regardless of the state of their logical volume
206 Check and fix the file system non-interactively (\fBpreen\fR). Exit immediately
207 if there is a problem that requires intervention. This option is required to
208 enable parallel file system checking.
217 Check writable file systems only.
225 \fB\fB/etc/vfstab\fR\fR
228 List of default parameters for each file system.
233 \fBfsck\fR(1M), \fBfsdb_udfs\fR(1M), \fBfstyp\fR(1M), \fBmkfs\fR(1M),
234 \fBmkfs_udfs\fR(1M), \fBmountall\fR(1M), \fBreboot\fR(1M), \fBvfstab\fR(4),
238 The operating system buffers file system data. Running \fBfsck\fR on a mounted
239 file system can cause the operating system's buffers to become out of date with
240 respect to the disk. For this reason, use \fBfsck\fR only when the file system
241 is unmounted. If this is not possible, take care that the system is quiescent
242 and that it is rebooted immediately after running \fBfsck\fR. A panic will
243 probably occur if running \fBfsck\fR on a file system that modifies the file
244 system while it is mounted.
247 If an unmount of the file system is not done before the system is shut down,
248 the file system might become corrupted. In this case, a file system check needs
249 to be completed before the next mount operation.
257 You cannot write to the device.
263 \fBCurrently Mounted on\fR
267 The device is already mounted and cannot run \fBfsck\fR.
273 \fBFILE SYSTEM WAS MODIFIED\fR
277 File system has been modified to bring it to a consistent state.
283 \fBCan't read allocation extent\fR
287 Cannot read the block containing allocation extent.
293 \fBBad tag on alloc extent\fR
297 Invalid tag detected when expecting an allocation extent.
303 \fBVolume sequence tag error\fR
307 Invalid tag detected in the volume sequence.
313 \fBSpace bitmap tag error\fR
317 Invalid tag detected in the space bitmap.
323 \fBUNEXPECTED INCONSISTENCY; RUN fsck MANUALLY\fR
327 Use \fBfsck\fR in interactive mode.