Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/fsck.1m
+++ new/usr/src/man/man1m/fsck.1m
1 1 '\" te
2 2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
3 +.\" Copyright 2015 Nexenta Systems, Inc. All rights reserved.
3 4 .\" Copyright 1989 AT&T
4 5 .\" 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.
5 6 .\" 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.
6 7 .\" 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]
7 -.TH FSCK 1M "May 7, 2008"
8 +.TH FSCK 1M "Sep 8, 2015"
8 9 .SH NAME
9 10 fsck \- check and repair file systems
10 11 .SH SYNOPSIS
11 12 .LP
12 13 .nf
13 14 \fBfsck\fR [\fB-F\fR \fIFSType\fR] [\fB-m\fR] [\fB-V\fR] [\fB-v\fR] [\fIspecial\fR]...
14 15 .fi
15 16
16 17 .LP
17 18 .nf
18 19 \fBfsck\fR [\fB-F\fR \fIFSType\fR] [\fB-n\fR | N | y | Y] [\fB-V\fR] [\fB-v\fR]
19 20 [\fB-o\fR \fIFSType-specific-options\fR] [\fIspecial\fR]...
20 21 .fi
21 22
22 23 .SH DESCRIPTION
23 24 .sp
24 25 .LP
25 26 \fBfsck\fR audits and interactively repairs inconsistent file system
26 27 conditions. If the file system is inconsistent the default action for each
27 28 correction is to wait for the user to respond \fByes\fR or \fBno\fR. If the
28 29 user does not have write permission \fBfsck\fR defaults to a \fBno\fR action.
29 30 Some corrective actions will result in loss of data. The amount and severity of
30 31 data loss can be determined from the diagnostic output.
31 32 .sp
32 33 .LP
33 34 \fIFSType-specific-options\fR are options specified in a comma-separated (with
34 35 no intervening spaces) list of options or keyword-attribute pairs for
35 36 interpretation by the \fIFSType-\fRspecific module of the command.
36 37 .sp
37 38 .LP
38 39 \fIspecial\fR represents the character special device on which the file system
39 40 resides, for example, \fB/dev/rdsk/c1t0d0s7\fR. Note: the character special
40 41 device, not the block special device, should be used. \fBfsck\fR will not work
41 42 if the block device is mounted.
42 43 .sp
43 44 .LP
44 45 If no \fIspecial\fR device is specified \fBfsck\fR checks the file systems
45 46 listed in \fB/etc/vfstab\fR. Those entries in \fB/etc/vfstab\fR which have a
46 47 character special device entry in the \fBfsckdev\fR field and have a non-zero
47 48 numeric entry in the \fBfsckpass\fR field will be checked. Specifying \fB-F\fR
48 49 \fIFSType\fR limits the file systems to be checked to those of the type
49 50 indicated.
50 51 .sp
51 52 .LP
52 53 If \fIspecial\fR is specified, but \fB-F\fR is not, the file system type will
53 54 be determined by looking for a matching entry in \fB/etc/vfstab\fR. If no entry
54 55 is found, the default local file system type specified in \fB/etc/default/fs\fR
55 56 will be used.
56 57 .sp
57 58 .LP
58 59 If a file system type supports parallel checking, for example, \fBufs,\fR some
59 60 file systems eligible for checking may be checked in parallel. Consult the file
60 61 system-specific man page (for example, \fBfsck_ufs\fR(1M)) for more
61 62 information.
62 63 .SH OPTIONS
63 64 .sp
64 65 .LP
65 66 The following generic options are supported:
66 67 .sp
67 68 .ne 2
68 69 .na
69 70 \fB\fB-F\fR \fIFSType\fR\fR
70 71 .ad
71 72 .sp .6
72 73 .RS 4n
73 74 Specify the file system type on which to operate.
74 75 .RE
75 76
76 77 .sp
77 78 .ne 2
78 79 .na
79 80 \fB\fB-m\fR\fR
80 81 .ad
81 82 .sp .6
82 83 .RS 4n
83 84 Check but do not repair. This option checks that the file system is suitable
84 85 for mounting, returning the appropriate exit status. If the file system is
85 86 ready for mounting, \fBfsck\fR displays a message such as:
86 87 .sp
87 88 .in +2
88 89 .nf
89 90 ufs fsck: sanity check: /dev/rdsk/c0t3d0s1 okay
90 91 .fi
91 92 .in -2
92 93 .sp
93 94
94 95 .RE
95 96
96 97 .sp
97 98 .ne 2
98 99 .na
99 100 \fB\fB-n\fR | \fB-N\fR\fR
100 101 .ad
101 102 .sp .6
102 103 .RS 4n
103 104 Assume a \fBno\fR response to all questions asked by \fBfsck\fR; do not open
104 105 the file system for writing.
105 106 .RE
106 107
107 108 .sp
108 109 .ne 2
109 110 .na
110 111 \fB\fB-V\fR\fR
111 112 .ad
112 113 .sp .6
113 114 .RS 4n
114 115 Echo the expanded command line but do not execute the command. This option may
115 116 be used to verify and to validate the command line.
116 117 .RE
117 118
118 119 .sp
119 120 .ne 2
120 121 .na
121 122 \fB\fB-v\fR\fR
122 123 .ad
123 124 .sp .6
124 125 .RS 4n
125 126 Enables verbose output. Might not be supported by all filesystem-specific
126 127 \fBfsck\fR implementations.
127 128 .RE
128 129
129 130 .sp
130 131 .ne 2
131 132 .na
132 133 \fB\fB-y\fR | \fBY\fR\fR
133 134 .ad
134 135 .sp .6
135 136 .RS 4n
136 137 Assume a \fByes\fR response to all questions asked by \fBfsck\fR.
137 138 .RE
138 139
139 140 .sp
140 141 .ne 2
141 142 .na
142 143 \fB\fB-o\fR \fIspecific-options\fR\fR
143 144 .ad
144 145 .sp .6
145 146 .RS 4n
146 147 These \fIspecific-options\fR can be any combination of the following separated
147 148 by commas (with no intervening spaces).
148 149 .sp
149 150 .ne 2
150 151 .na
151 152 \fB\fBb=\fR\fIn\fR\fR
152 153 .ad
153 154 .sp .6
154 155 .RS 4n
155 156 Use block \fIn\fR as the super block for the file system. Block 32 is always
156 157 one of the alternate super blocks. Determine the location of other super blocks
157 158 by running \fBnewfs\fR(1M) with the \fB-Nv\fR options specified.
158 159 .RE
159 160
160 161 .sp
161 162 .ne 2
162 163 .na
163 164 \fB\fBc\fR\fR
164 165 .ad
165 166 .sp .6
166 167 .RS 4n
167 168 If the file system is in the old (static table) format, convert it to the new
168 169 (dynamic table) format. If the file system is in the new format, convert it to
169 170 the old format provided the old format can support the file system
170 171 configuration. In interactive mode, \fBfsck\fR will list the direction the
171 172 conversion is to be made and ask whether the conversion should be done. If a
172 173 negative answer is given, no further operations are done on the file system. In
173 174 preen mode, the direction of the conversion is listed and done if possible
174 175 without user interaction. Conversion in preen mode is best used when all the
175 176 file systems are being converted at once. The format of a file system can be
176 177 determined from the first line of output from \fBfstyp\fR(1M). Note: the
177 178 \fBc\fR option is seldom used and is included only for compatibility with
178 179 pre-4.1 releases. There is no guarantee that this option will be included in
179 180 future releases.
180 181 .RE
181 182
182 183 .sp
183 184 .ne 2
184 185 .na
185 186 \fB\fBf\fR\fR
186 187 .ad
187 188 .sp .6
188 189 .RS 4n
189 190 Force checking of file systems regardless of the state of their super block
190 191 clean flag.
191 192 .RE
192 193
193 194 .sp
194 195 .ne 2
195 196 .na
196 197 \fB\fBp\fR\fR
197 198 .ad
198 199 .sp .6
199 200 .RS 4n
200 201 Check and fix the file system non-interactively ("preen"). Exit immediately if
201 202 there is a problem requiring intervention. This option is required to enable
202 203 parallel file system checking.
203 204 .RE
204 205
205 206 .sp
206 207 .ne 2
207 208 .na
208 209 \fB\fBw\fR\fR
209 210 .ad
210 211 .sp .6
211 212 .RS 4n
212 213 Check writable file systems only.
213 214 .RE
214 215
215 216 .RE
216 217
217 218 .SH EXIT STATUS
218 219 .sp
219 220 .ne 2
220 221 .na
221 222 \fB\fB0\fR\fR
222 223 .ad
223 224 .sp .6
224 225 .RS 4n
225 226 file system is unmounted and OK
226 227 .RE
227 228
228 229 .sp
229 230 .ne 2
230 231 .na
231 232 \fB\fB1\fR\fR
232 233 .ad
233 234 .sp .6
234 235 .RS 4n
235 236 erroneous parameters are specified
236 237 .RE
237 238
238 239 .sp
239 240 .ne 2
240 241 .na
241 242 \fB\fB32\fR\fR
242 243 .ad
243 244 .sp .6
244 245 .RS 4n
245 246 file system is unmounted and needs checking (\fBfsck\fR \fB-m\fR only)
246 247 .RE
247 248
248 249 .sp
249 250 .ne 2
250 251 .na
251 252 \fB\fB33\fR\fR
252 253 .ad
253 254 .sp .6
254 255 .RS 4n
255 256 file system is already mounted
256 257 .RE
257 258
258 259 .sp
259 260 .ne 2
260 261 .na
261 262 \fB\fB34\fR\fR
262 263 .ad
263 264 .sp .6
264 265 .RS 4n
265 266 cannot stat device
266 267 .RE
267 268
268 269 .sp
269 270 .ne 2
270 271 .na
271 272 \fB\fB35\fR\fR
272 273 .ad
273 274 .sp .6
274 275 .RS 4n
275 276 a filesystem that is mounted read/write was modified - reboot
276 277 .RE
277 278
278 279 .sp
279 280 .ne 2
280 281 .na
281 282 \fB\fB36\fR\fR
282 283 .ad
283 284 .sp .6
284 285 .RS 4n
285 286 uncorrectable errors detected - terminate normally
286 287 .RE
287 288
288 289 .sp
289 290 .ne 2
290 291 .na
291 292 \fB\fB37\fR\fR
292 293 .ad
293 294 .sp .6
294 295 .RS 4n
295 296 a signal was caught during processing
296 297 .RE
297 298
298 299 .sp
299 300 .ne 2
300 301 .na
301 302 \fB\fB39\fR\fR
302 303 .ad
303 304 .sp .6
304 305 .RS 4n
305 306 uncorrectable errors detected - terminate immediately
306 307 .RE
307 308
308 309 .sp
309 310 .ne 2
310 311 .na
311 312 \fB\fB40\fR\fR
312 313 .ad
313 314 .sp .6
314 315 .RS 4n
315 316 file system is mounted read-only and is OK
316 317 .RE
317 318
318 319 .SH USAGE
319 320 .sp
320 321 .LP
321 322 The \fBfsck\fR command is \fBlarge file aware\fR for UFS file systems, per the
322 323 \fBlargefile\fR(5) man page.
323 324 .SH FILES
324 325 .sp
325 326 .ne 2
326 327 .na
327 328 \fB\fB/etc/default/fs\fR\fR
328 329 .ad
329 330 .sp .6
330 331 .RS 4n
331 332 default local file system type. Default values can be set for the following
332 333 flags in \fB/etc/default/fs\fR. For example: \fBLOCAL=ufs.\fR
333 334 .sp
334 335 .ne 2
335 336 .na
336 337 \fB\fBLOCAL\fR\fR
337 338 .ad
338 339 .sp .6
339 340 .RS 4n
340 341 The default partition for a command if no FSType is specified.
341 342 .RE
342 343
343 344 .RE
344 345
345 346 .sp
346 347 .ne 2
347 348 .na
348 349 \fB\fB/etc/vfstab\fR\fR
349 350 .ad
350 351 .sp .6
351 352 .RS 4n
352 353 list of default parameters for each file system
353 354 .RE
354 355
355 356 .SH ATTRIBUTES
356 357 .sp
357 358 .LP
358 359 See \fBattributes\fR(5) for descriptions of the following attributes:
359 360 .sp
360 361
361 362 .sp
362 363 .TS
363 364 box;
|
↓ open down ↓ |
346 lines elided |
↑ open up ↑ |
364 365 c | c
365 366 l | l .
366 367 ATTRIBUTE TYPE ATTRIBUTE VALUE
367 368 _
368 369 Interface Stability Committed
369 370 .TE
370 371
371 372 .SH SEE ALSO
372 373 .sp
373 374 .LP
374 -\fBclri\fR(1M), \fBfsck_cachefs\fR(1M), \fBfsck_ufs\fR(1M), \fBfsdb_ufs\fR(1M),
375 +\fBclri\fR(1M), \fBfsck_ufs\fR(1M), \fBfsdb_ufs\fR(1M),
375 376 \fBfsirand\fR(1M), \fBfstyp\fR(1M), \fBmkfs\fR(1M), \fBmkfs_ufs\fR(1M),
376 377 \fBmountall\fR(1M), \fBnewfs\fR(1M), \fBreboot\fR( 1M), \fBvfstab\fR(4),
377 378 \fBattributes\fR(5), \fBlargefile\fR(5), \fBufs\fR(7FS)
378 379 .SH WARNINGS
379 380 .sp
380 381 .LP
381 382 The operating system buffers file system data. Running \fBfsck\fR on a mounted
382 383 file system can cause the operating system's buffers to become out of date with
383 384 respect to the disk. For this reason, the file system should be \fIunmounted\fR
384 385 when \fBfsck\fR is used. If this is not possible, care should be taken that the
385 386 system is quiescent and that it is rebooted immediately after \fBfsck\fR is
386 387 run. Quite often, however, this will not be sufficient. A panic will probably
387 388 occur if running \fBfsck\fR on a file system modifies the file system.
388 389 .SH NOTES
389 390 .sp
390 391 .LP
391 392 This command may not be supported for all \fIFSTypes\fR.
392 393 .sp
393 394 .LP
394 395 Starting with Solaris 9, \fBfsck\fR manages extended attribute data on the
395 396 disk. (See \fBfsattr\fR(5) for a description of extended file attributes.) A
396 397 file system with extended attributes can be mounted on versions of Solaris that
397 398 are not attribute-aware (versions prior to Solaris 9), but the attributes will
398 399 not be accessible and \fBfsck\fR will strip them from the files and place them
399 400 in \fBlost+found\fR. Once the attributes have been stripped, the file system is
400 401 completely stable on versions of Solaris that are not attribute-aware, but
401 402 would be considered corrupted on attribute-aware versions. In the latter
402 403 circumstance, run the attribute-aware \fBfsck\fR to stabilize the file system
403 404 before using it in an attribute-aware environment.
|
↓ open down ↓ |
19 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX