1fsck_udfs(1M) System Administration Commands fsck_udfs(1M)
2
3
4
6 fsck_udfs - file system consistency check and interactive repair
7
9 fsck -F udfs [generic_options] [special ...]
10
11
12 fsck -F udfs [generic_options] [-o specific_options]
13 [special ...]
14
15
17 fsck audits and interactively repairs inconsistent conditions on file
18 systems. A file system to be checked can be specified by giving the
19 name of the block or character special device or by giving the name of
20 its mount point if a matching entry exists in /etc/vfstab.
21
22
23 special represents the character special device, for example,
24 /dev/rdsk/c0t2d0s0, on which the file system resides. The character
25 special device, not the block special device should be used. fsck does
26 not work on a mounted block device.
27
28
29 If no special device is specified, all udfs file systems specified in
30 the vfstab file with a fsckdev entry are checked. If the -p (preen)
31 option is specified, udfs file systems with an fsckpass number greater
32 than 1 are checked in parallel. See fsck(1M).
33
34
35 In the case of correcting serious inconsistencies, by default, fsck
36 asks for confirmation before making a repair and waits for the operator
37 to respond with either yes or no. If the operator does not have write
38 permission on the file system, fsck defaults to the -n (no corrections)
39 option. See fsck(1M).
40
41
42 Repairing some file system inconsistencies can result in loss of data.
43 The amount and severity of data loss can be determined from the diag‐
44 nostic output.
45
46
47 fsck automatically corrects innocuous inconsistencies. It displays a
48 message for each corrected inconsistency that identifies the nature of
49 the correction which took place on the file system. After successfully
50 correcting a file system, fsck prints the number of files on that file
51 system and the number of used and free blocks.
52
53
54 Inconsistencies checked are as follows:
55
56 o Blocks claimed by more than one file or the free list
57
58 o Blocks claimed by a file or the free list outside the range
59 of the file system
60
61 o Incorrect link counts in file entries
62
63 o Incorrect directory sizes
64
65 o Bad file entry format
66
67 o Blocks not accounted for anywhere
68
69 o Directory checks, file pointing to unallocated file entry
70 and absence of a parent directory entry
71
72 o Descriptor checks, more blocks for files than there are in
73 the file system
74
75 o Bad free block list format
76
77 o Total free block count incorrect
78
80 The following options are supported:
81
82 generic_options The following generic_options are supported:
83
84 -m Check but do not repair. This option
85 checks to be sure that the file sys‐
86 tem is suitable for mounting, and
87 returns the appropriate exit status.
88 If the file system is ready for
89 mounting, fsck displays a message
90 such as:
91
92 udfs fsck: sanity check: /dev/rdsk/c0t2d0s0 okay
93
94
95
96
97 -n | -N Assume a no response to all questions
98 asked by fsck; do not open the file
99 system for writing.
100
101
102 -V Echo the expanded command line, but
103 do not execute the command. This
104 option can be used to verify and to
105 validate the command line.
106
107
108 -y | -Y Assume a yes response to all ques‐
109 tions asked by fsck.
110
111
112
113 -o specific_options Specify udfs file system specific options in a
114 comma-separated list with no intervening spaces.
115 The following specific_options are available:
116
117 f Force checking of file systems regardless
118 of the state of their logical volume
119 integrity state.
120
121
122 p Check and fix the file system non-interac‐
123 tively (preen). Exit immediately if there
124 is a problem that requires intervention.
125 This option is required to enable parallel
126 file system checking.
127
128
129 w Check writable file systems only.
130
131
132
134 /etc/vtstab List of default parameters for each file system.
135
136
138 See attributes(5) for descriptions of the following attributes:
139
140
141
142
143 ┌─────────────────────────────┬─────────────────────────────┐
144 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
145 ├─────────────────────────────┼─────────────────────────────┤
146 │Availability │SUNWudf │
147 └─────────────────────────────┴─────────────────────────────┘
148
150 fsck(1M), fsdb_udfs(1M), fstyp(1M), mkfs(1M), mkfs_udfs(1M), moun‐
151 tall(1M), reboot(1M), vfstab(4), attributes(5)
152
154 The operating system buffers file system data. Running fsck on a
155 mounted file system can cause the operating system's buffers to become
156 out of date with respect to the disk. For this reason, use fsck only
157 when the file system is unmounted. If this is not possible, take care
158 that the system is quiescent and that it is rebooted immediately after
159 running fsck. A panic will probably occur if running fsck on a file
160 system that modifies the file system while it is mounted.
161
162
163 If an unmount of the file system is not done before the system is shut
164 down, the file system might become corrupted. In this case, a file sys‐
165 tem check needs to be completed before the next mount operation.
166
168 not writable
169
170 You cannot write to the device.
171
172
173 Currently Mounted on
174
175 The device is already mounted and cannot run fsck.
176
177
178 FILE SYSTEM WAS MODIFIED
179
180 File system has been modified to bring it to a consistent state.
181
182
183 Can't read allocation extent
184
185 Cannot read the block containing allocation extent.
186
187
188 Bad tag on alloc extent
189
190 Invalid tag detected when expecting an allocation extent.
191
192
193 Volume sequence tag error
194
195 Invalid tag detected in the volume sequence.
196
197
198 Space bitmap tag error
199
200 Invalid tag detected in the space bitmap.
201
202
203 UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
204
205 Use fsck in interactive mode.
206
207
208
209
210SunOS 5.11 5 September 2000 fsck_udfs(1M)