Commit | Line | Data |
---|---|---|
a38b2411 KM |
1 | .\" Copyright (c) 1982 Regents of the University of California. |
2 | .\" All rights reserved. The Berkeley software License Agreement | |
3 | .\" specifies the terms and conditions for redistribution. | |
4 | .\" | |
5 | .\" @(#)4.t 4.1 (Berkeley) %G% | |
6 | .\" | |
7 | .ds RH Appendix A \- Fsck Error Conditions | |
8 | .NH | |
9 | Appendix A \- Fsck Error Conditions | |
10 | .NH 2 | |
11 | Conventions | |
12 | .PP | |
13 | .I Fsck | |
14 | is | |
15 | a multi-pass file system check program. | |
16 | Each file system pass invokes a different Phase of the | |
17 | .I fsck | |
18 | program. | |
19 | After the initial setup, | |
20 | .I fsck | |
21 | performs successive Phases over each file system, | |
22 | checking blocks and sizes, | |
23 | path-names, | |
24 | connectivity, | |
25 | reference counts, | |
26 | and the map of free blocks, | |
27 | (possibly rebuilding it), | |
28 | and performs some cleanup. | |
29 | .LP | |
30 | Normally | |
31 | .I fsck | |
32 | is run non-interactively to | |
33 | .I preen | |
34 | the file systems after an unclean halt. | |
35 | While preen'ing a file system, | |
36 | it will only fix corruptions that are expected | |
37 | to occur from an unclean halt. | |
38 | These actions are a proper subset of the actions that | |
39 | .I fsck | |
40 | will take when it is running interactively. | |
41 | Throughout this appendix many errors have several options | |
42 | that the operator can take. | |
43 | When an inconsistency is detected, | |
44 | .I fsck | |
45 | reports the error condition to the operator. | |
46 | If a response is required, | |
47 | .I fsck | |
48 | prints a prompt message and | |
49 | waits for a response. | |
50 | When preen'ing most errors are fatal. | |
51 | For those that are expected, | |
52 | the response taken is noted. | |
53 | This appendix explains the meaning of each error condition, | |
54 | the possible responses, and the related error conditions. | |
55 | .LP | |
56 | The error conditions are organized by the | |
57 | .I Phase | |
58 | of the | |
59 | .I fsck | |
60 | program in which they can occur. | |
61 | The error conditions that may occur | |
62 | in more than one Phase | |
63 | will be discussed in initialization. | |
64 | .NH 2 | |
65 | Initialization | |
66 | .PP | |
67 | Before a file system check can be performed, certain | |
68 | tables have to be set up and certain files opened. | |
69 | This section concerns itself with the opening of files and | |
70 | the initialization of tables. | |
71 | This section lists error conditions resulting from | |
72 | command line options, | |
73 | memory requests, | |
74 | opening of files, | |
75 | status of files, | |
76 | file system size checks, | |
77 | and creation of the scratch file. | |
78 | All of the initialization errors are fatal | |
79 | when the file system is being preen'ed. | |
80 | .sp | |
81 | .LP | |
82 | .B "\fIC\fP option?" | |
83 | .br | |
84 | \fIC\fP is not a legal option to | |
85 | .I fsck ; | |
86 | legal options are \-b, \-y, \-n, and \-p. | |
87 | .I Fsck | |
88 | terminates on this error condition. | |
89 | See the | |
90 | .I fsck (8) | |
91 | manual entry for further detail. | |
92 | .sp | |
93 | .LP | |
94 | .B "cannot alloc NNN bytes for blockmap" | |
95 | .br | |
96 | .B "cannot alloc NNN bytes for freemap" | |
97 | .br | |
98 | .B "cannot alloc NNN bytes for statemap" | |
99 | .br | |
100 | .B "cannot alloc NNN bytes for lncntp" | |
101 | .br | |
102 | .I Fsck 's | |
103 | request for memory for its virtual | |
104 | memory tables failed. | |
105 | This should never happen. | |
106 | .I Fsck | |
107 | terminates on this error condition. | |
108 | See a guru. | |
109 | .sp | |
110 | .LP | |
111 | .B "Can't open checklist file: \fIF\fP" | |
112 | .br | |
113 | The file system checklist file | |
114 | \fIF\fP (usually | |
115 | .I /etc/fstab ) | |
116 | can not be opened for reading. | |
117 | .I Fsck | |
118 | terminates on this error condition. | |
119 | Check access modes of \fIF\fP. | |
120 | .sp | |
121 | .LP | |
122 | .B "Can't stat root" | |
123 | .br | |
124 | .I Fsck 's | |
125 | request for statistics about the root directory ``/'' failed. | |
126 | This should never happen. | |
127 | .I Fsck | |
128 | terminates on this error condition. | |
129 | See a guru. | |
130 | .sp | |
131 | .LP | |
132 | .B "Can't stat \fIF\fP" | |
133 | .br | |
134 | .B "Can't make sense out of name \fIF\fP" | |
135 | .br | |
136 | .I Fsck 's | |
137 | request for statistics about the file system \fIF\fP failed. | |
138 | When running manually, | |
139 | it ignores this file system | |
140 | and continues checking the next file system given. | |
141 | Check access modes of \fIF\fP. | |
142 | .sp | |
143 | .LP | |
144 | .B "Can't open \fIF\fP" | |
145 | .br | |
146 | .I Fsck 's | |
147 | request attempt to open the file system \fIF\fP failed. | |
148 | When running manually, it ignores this file system | |
149 | and continues checking the next file system given. | |
150 | Check access modes of \fIF\fP. | |
151 | .sp | |
152 | .LP | |
153 | .B "\fIF\fP: (NO WRITE)" | |
154 | .br | |
155 | Either the \-n flag was specified or | |
156 | .I fsck 's | |
157 | attempt to open the file system \fIF\fP for writing failed. | |
158 | When running manually, | |
159 | all the diagnostics are printed out, | |
160 | but no modifications are attempted to fix them. | |
161 | .sp | |
162 | .LP | |
163 | .B "file is not a block or character device; OK" | |
164 | .br | |
165 | You have given | |
166 | .I fsck | |
167 | a regular file name by mistake. | |
168 | Check the type of the file specified. | |
169 | .LP | |
170 | Possible responses to the OK prompt are: | |
171 | .IP YES | |
172 | Ignore this error condition. | |
173 | .IP NO | |
174 | ignore this file system and continues checking | |
175 | the next file system given. | |
176 | .sp | |
177 | .LP | |
178 | One of the following messages will appear: | |
179 | .br | |
180 | .B "MAGIC NUMBER WRONG" | |
181 | .br | |
182 | .B "NCG OUT OF RANGE" | |
183 | .br | |
184 | .B "CPG OUT OF RANGE" | |
185 | .br | |
186 | .B "NCYL DOES NOT JIVE WITH NCG*CPG" | |
187 | .br | |
188 | .B "SIZE PREPOSTEROUSLY LARGE" | |
189 | .br | |
190 | .B "TRASHED VALUES IN SUPER BLOCK" | |
191 | .sp | |
192 | and will be followed by the message: | |
193 | .br | |
194 | .B "\fIF\fP: BAD SUPER BLOCK: \fIB\fP" | |
195 | .br | |
196 | .B "USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE" | |
197 | .br | |
198 | .B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8)." | |
199 | .br | |
200 | The super block has been corrupted. | |
201 | An alternative super block must be selected from among those | |
202 | listed by | |
203 | .I newfs | |
204 | (8) when the file system was created. | |
205 | For file systems with a blocksize less than 32K, | |
206 | specifying \-b 32 is a good first choice. | |
207 | .sp | |
208 | .LP | |
209 | .B "INTERNAL INCONSISTENCY: \fIM\fP" | |
210 | .br | |
211 | .I Fsck 's | |
212 | has had an internal panic, whose message is specified as \fIM\fP. | |
213 | This should never happen. | |
214 | See a guru. | |
215 | .sp | |
216 | .LP | |
217 | .B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)" | |
218 | .br | |
219 | .I Fsck 's | |
220 | request for moving to a specified block number \fIB\fP in | |
221 | the file system failed. | |
222 | This should never happen. | |
223 | See a guru. | |
224 | .LP | |
225 | Possible responses to the CONTINUE prompt are: | |
226 | .IP YES | |
227 | attempt to continue to run the file system check. | |
228 | Often, | |
229 | however the problem will persist. | |
230 | This error condition will not allow a complete check of the file system. | |
231 | A second run of | |
232 | .I fsck | |
233 | should be made to re-check this file system. | |
234 | If the block was part of the virtual memory buffer | |
235 | cache, | |
236 | .I fsck | |
237 | will terminate with the message ``Fatal I/O error''. | |
238 | .IP NO | |
239 | terminate the program. | |
240 | .sp | |
241 | .LP | |
242 | .B "CAN NOT READ: BLK \fIB\fP (CONTINUE)" | |
243 | .br | |
244 | .I Fsck 's | |
245 | request for reading a specified block number \fIB\fP in | |
246 | the file system failed. | |
247 | This should never happen. | |
248 | See a guru. | |
249 | .LP | |
250 | Possible responses to the CONTINUE prompt are: | |
251 | .IP YES | |
252 | attempt to continue to run the file system check. | |
253 | Often, | |
254 | however, | |
255 | the problem will persist. | |
256 | This error condition will not allow a complete check of the file system. | |
257 | A second run of | |
258 | .I fsck | |
259 | should be made to re-check this file system. | |
260 | If the block was part of the virtual memory buffer | |
261 | cache, | |
262 | .I fsck | |
263 | will terminate with the message ``Fatal I/O error''. | |
264 | .IP NO | |
265 | terminate the program. | |
266 | .sp | |
267 | .LP | |
268 | .B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)" | |
269 | .br | |
270 | .I Fsck 's | |
271 | request for writing a specified block number \fIB\fP | |
272 | in the file system failed. | |
273 | The disk is write-protected. | |
274 | See a guru. | |
275 | .LP | |
276 | Possible responses to the CONTINUE prompt are: | |
277 | .IP YES | |
278 | attempt to continue to run the file system check. | |
279 | Often, | |
280 | however, | |
281 | the problem will persist. | |
282 | This error condition will not allow a complete check of the file system. | |
283 | A second run of | |
284 | .I fsck | |
285 | should be made to re-check this file system. | |
286 | If the block was part of the virtual memory buffer | |
287 | cache, | |
288 | .I fsck | |
289 | will terminate with the message ``Fatal I/O error''. | |
290 | .IP NO | |
291 | terminate the program. | |
292 | .NH 2 | |
293 | Phase 1 \- Check Blocks and Sizes | |
294 | .PP | |
295 | This phase concerns itself with | |
296 | the inode list. | |
297 | This section lists error conditions resulting from | |
298 | checking inode types, | |
299 | setting up the zero-link-count table, | |
300 | examining inode block numbers for bad or duplicate blocks, | |
301 | checking inode size, | |
302 | and checking inode format. | |
303 | All errors in this phase except | |
304 | .B "INCORRECT BLOCK COUNT" | |
305 | are fatal if the file system is being preen'ed, | |
306 | .sp | |
307 | .LP | |
308 | .B "CG \fIC\fP: BAD MAGIC NUMBER" | |
309 | The magic number of cylinder group \fIC\fP is wrong. | |
310 | This usually indicates that the cylinder group maps have been destroyed. | |
311 | When running manually the cylinder group is marked as needing | |
312 | to be reconstructed. | |
313 | .sp | |
314 | .LP | |
315 | .B "UNKNOWN FILE TYPE I=\fII\fP (CLEAR)" | |
316 | The mode word of the inode \fII\fP indicates that the inode is not a | |
317 | special block inode, special character inode, socket inode, regular inode, | |
318 | symbolic link, or directory inode. | |
319 | .LP | |
320 | Possible responses to the CLEAR prompt are: | |
321 | .IP YES | |
322 | de-allocate inode \fII\fP by zeroing its contents. | |
323 | This will always invoke the UNALLOCATED error condition in Phase 2 | |
324 | for each directory entry pointing to this inode. | |
325 | .IP NO | |
326 | ignore this error condition. | |
327 | .sp | |
328 | .LP | |
329 | .B "LINK COUNT TABLE OVERFLOW (CONTINUE)" | |
330 | .br | |
331 | An internal table for | |
332 | .I fsck | |
333 | containing allocated inodes with a link count of | |
334 | zero has no more room. | |
335 | Recompile | |
336 | .I fsck | |
337 | with a larger value of MAXLNCNT. | |
338 | .LP | |
339 | Possible responses | |
340 | to the CONTINUE prompt are: | |
341 | .IP YES | |
342 | continue with the program. | |
343 | This error condition will not allow a complete check of the file system. | |
344 | A second run of | |
345 | .I fsck | |
346 | should be made to re-check this file system. | |
347 | If another allocated inode with a zero link count is found, | |
348 | this error condition is repeated. | |
349 | .IP NO | |
350 | terminate the program. | |
351 | .sp | |
352 | .LP | |
353 | .B "\fIB\fP BAD I=\fII\fP" | |
354 | .br | |
355 | Inode \fII\fP contains block number \fIB\fP with a number | |
356 | lower than the number of the first data block in the file system or | |
357 | greater than the number of the last block | |
358 | in the file system. | |
359 | This error condition may invoke the | |
360 | .B "EXCESSIVE BAD BLKS" | |
361 | error condition in Phase 1 if | |
362 | inode \fII\fP has too many block numbers outside the file system range. | |
363 | This error condition will always invoke the | |
364 | .B "BAD/DUP" | |
365 | error condition in Phase 2 and Phase 4. | |
366 | .sp | |
367 | .LP | |
368 | .B "EXCESSIVE BAD BLKS I=\fII\fP (CONTINUE)" | |
369 | .br | |
370 | There is more than a tolerable number (usually 10) of blocks with a number | |
371 | lower than the number of the first data block in the file system or greater than | |
372 | the number of last block in the file system associated with inode \fII\fP. | |
373 | .LP | |
374 | Possible responses to the CONTINUE prompt are: | |
375 | .IP YES | |
376 | ignore the rest of the blocks in this inode | |
377 | and continue checking with the next inode in the file system. | |
378 | This error condition will not allow a complete check of the file system. | |
379 | A second run of | |
380 | .I fsck | |
381 | should be made to re-check this file system. | |
382 | .IP NO | |
383 | terminate the program. | |
384 | .sp | |
385 | .LP | |
386 | .B "\fIB\fP DUP I=\fII\fP" | |
387 | .br | |
388 | Inode \fII\fP contains block number \fIB\fP which is already claimed by | |
389 | another inode. | |
390 | This error condition may invoke the | |
391 | .B "EXCESSIVE DUP BLKS" | |
392 | error condition in Phase 1 if | |
393 | inode \fII\fP has too many block numbers claimed by other inodes. | |
394 | This error condition will always invoke Phase 1b and the | |
395 | .B "BAD/DUP" | |
396 | error condition in Phase 2 and Phase 4. | |
397 | .sp | |
398 | .LP | |
399 | .B "EXCESSIVE DUP BLKS I=\fII\fP (CONTINUE)" | |
400 | .br | |
401 | There is more than a tolerable number (usually 10) of blocks claimed by other | |
402 | inodes. | |
403 | .LP | |
404 | Possible responses to the CONTINUE prompt are: | |
405 | .IP YES | |
406 | ignore the rest of the blocks in this inode | |
407 | and continue checking with the next inode in the file system. | |
408 | This error condition will not allow a complete check of the file system. | |
409 | A second run of | |
410 | .I fsck | |
411 | should be made to re-check this file system. | |
412 | .IP NO | |
413 | terminate the program. | |
414 | .sp | |
415 | .LP | |
416 | .B "DUP TABLE OVERFLOW (CONTINUE)" | |
417 | .br | |
418 | An internal table in | |
419 | .I fsck | |
420 | containing duplicate block numbers has no more room. | |
421 | Recompile | |
422 | .I fsck | |
423 | with a larger value of DUPTBLSIZE. | |
424 | .LP | |
425 | Possible responses to the CONTINUE prompt are: | |
426 | .IP YES | |
427 | continue with the program. | |
428 | This error condition will not allow a complete check of the file system. | |
429 | A second run of | |
430 | .I fsck | |
431 | should be made to re-check this file system. | |
432 | If another duplicate block is found, this error condition will repeat. | |
433 | .IP NO | |
434 | terminate the program. | |
435 | .sp | |
436 | .LP | |
437 | .B "PARTIALLY ALLOCATED INODE I=\fII\fP (CLEAR)" | |
438 | .br | |
439 | Inode \fII\fP is neither allocated nor unallocated. | |
440 | .LP | |
441 | Possible responses to the CLEAR prompt are: | |
442 | .IP YES | |
443 | de-allocate inode \fII\fP by zeroing its contents. | |
444 | .IP NO | |
445 | ignore this error condition. | |
446 | .sp | |
447 | .LP | |
448 | .B "INCORRECT BLOCK COUNT I=\fII\fP (\fIX\fP should be \fIY\fP) (CORRECT)" | |
449 | .br | |
450 | The block count for inode \fII\fP is \fIX\fP blocks, | |
451 | but should be \fIY\fP blocks. | |
452 | When preen'ing the count is corrected. | |
453 | .LP | |
454 | Possible responses to the CORRECT prompt are: | |
455 | .IP YES | |
456 | replace the block count of inode \fII\fP with \fIY\fP. | |
457 | .IP NO | |
458 | ignore this error condition. | |
459 | .NH 2 | |
460 | Phase 1B: Rescan for More Dups | |
461 | .PP | |
462 | When a duplicate block is found in the file system, the file system is | |
463 | rescanned to find the inode which previously claimed that block. | |
464 | This section lists the error condition when the duplicate block is found. | |
465 | .sp | |
466 | .LP | |
467 | .B "\fIB\fP DUP I=\fII\fP" | |
468 | .br | |
469 | Inode \fII\fP contains block number \fIB\fP that | |
470 | is already claimed by another inode. | |
471 | This error condition will always invoke the | |
472 | .B "BAD/DUP" | |
473 | error condition in Phase 2. | |
474 | You can determine which inodes have overlapping blocks by examining | |
475 | this error condition and the DUP error condition in Phase 1. | |
476 | .NH 2 | |
477 | Phase 2 \- Check Pathnames | |
478 | .PP | |
479 | This phase concerns itself with removing directory entries | |
480 | pointing to | |
481 | error conditioned inodes | |
482 | from Phase 1 and Phase 1b. | |
483 | This section lists error conditions resulting from | |
484 | root inode mode and status, | |
485 | directory inode pointers in range, | |
486 | and directory entries pointing to bad inodes. | |
487 | All errors in this phase are fatal if the file system is being preen'ed. | |
488 | .sp | |
489 | .LP | |
490 | .B "ROOT INODE UNALLOCATED. TERMINATING." | |
491 | .br | |
492 | The root inode (usually inode number 2) has no allocate mode bits. | |
493 | This should never happen. | |
494 | The program will terminate. | |
495 | .sp | |
496 | .LP | |
497 | .B "NAME TOO LONG \fIF\fP" | |
498 | .br | |
499 | An excessively long path name has been found. | |
500 | This is usually indicative of loops in the file system name space. | |
501 | This can occur if the super user has made circular links to directories. | |
502 | The offending links must be removed (by a guru). | |
503 | .sp | |
504 | .LP | |
505 | .B "ROOT INODE NOT DIRECTORY (FIX)" | |
506 | .br | |
507 | The root inode (usually inode number 2) | |
508 | is not directory inode type. | |
509 | .LP | |
510 | Possible responses to the FIX prompt are: | |
511 | .IP YES | |
512 | replace the root inode's type to be a directory. | |
513 | If the root inode's data blocks are not directory blocks, | |
514 | a VERY large number of error conditions will be produced. | |
515 | .IP NO | |
516 | terminate the program. | |
517 | .sp | |
518 | .LP | |
519 | .B "DUPS/BAD IN ROOT INODE (CONTINUE)" | |
520 | .br | |
521 | Phase 1 or Phase 1b have found duplicate blocks | |
522 | or bad blocks in the root inode (usually inode number 2) for the file system. | |
523 | .LP | |
524 | Possible responses to the CONTINUE prompt are: | |
525 | .IP YES | |
526 | ignore the | |
527 | .B "DUPS/BAD" | |
528 | error condition in the root inode and | |
529 | attempt to continue to run the file system check. | |
530 | If the root inode is not correct, | |
531 | then this may result in a large number of other error conditions. | |
532 | .IP NO | |
533 | terminate the program. | |
534 | .sp | |
535 | .LP | |
536 | .B "I OUT OF RANGE I=\fII\fP NAME=\fIF\fP (REMOVE)" | |
537 | .br | |
538 | A directory entry \fIF\fP has an inode number \fII\fP which is greater than | |
539 | the end of the inode list. | |
540 | .LP | |
541 | Possible responses to the REMOVE prompt are: | |
542 | .IP YES | |
543 | the directory entry \fIF\fP is removed. | |
544 | .IP NO | |
545 | ignore this error condition. | |
546 | .sp | |
547 | .LP | |
548 | .B "UNALLOCATED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (REMOVE)" | |
549 | .br | |
550 | A directory entry \fIF\fP has a directory inode \fII\fP | |
551 | without allocate mode bits. | |
552 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP, | |
553 | and directory name \fIF\fP are printed. | |
554 | .LP | |
555 | Possible responses to the REMOVE prompt are: | |
556 | .IP YES | |
557 | the directory entry \fIF\fP is removed. | |
558 | .IP NO | |
559 | ignore this error condition. | |
560 | .sp | |
561 | .LP | |
562 | .B "UNALLOCATED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP FILE=\fIF\fP (REMOVE)" | |
563 | .br | |
564 | A directory entry \fIF\fP has an inode \fII\fP | |
565 | without allocate mode bits. | |
566 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP, and file name \fIF\fP are printed. | |
567 | .LP | |
568 | Possible responses to the REMOVE prompt are: | |
569 | .IP YES | |
570 | the directory entry \fIF\fP is removed. | |
571 | .IP NO | |
572 | ignore this error condition. | |
573 | .sp | |
574 | .LP | |
575 | .B "DUP/BAD I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (REMOVE)" | |
576 | .br | |
577 | Phase 1 or Phase 1b have found duplicate blocks or bad blocks | |
578 | associated with directory entry \fIF\fP, directory inode \fII\fP. | |
579 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP, and directory name \fIF\fP are printed. | |
580 | .LP | |
581 | Possible responses to the REMOVE prompt are: | |
582 | .IP YES | |
583 | the directory entry \fIF\fP is removed. | |
584 | .IP NO | |
585 | ignore this error condition. | |
586 | .sp | |
587 | .LP | |
588 | .B "DUP/BAD I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP FILE=\fIF\fP (REMOVE)" | |
589 | .br | |
590 | Phase 1 or Phase 1b have found duplicate blocks or bad blocks | |
591 | associated with directory entry \fIF\fP, inode \fII\fP. | |
592 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, | |
593 | modify time \fIT\fP, and file name \fIF\fP are printed. | |
594 | .LP | |
595 | Possible responses to the REMOVE prompt are: | |
596 | .IP YES | |
597 | the directory entry \fIF\fP is removed. | |
598 | .IP NO | |
599 | ignore this error condition. | |
600 | .sp | |
601 | .LP | |
602 | .B "ZERO LENGTH DIRECTORY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (REMOVE)" | |
603 | .br | |
604 | A directory entry \fIF\fP has a size \fIS\fP that is zero. | |
605 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP, | |
606 | and directory name \fIF\fP are printed. | |
607 | .LP | |
608 | Possible responses to the REMOVE prompt are: | |
609 | .IP YES | |
610 | the directory entry \fIF\fP is removed; | |
611 | this will always invoke the BAD/DUP error condition in Phase 4. | |
612 | .IP NO | |
613 | ignore this error condition. | |
614 | .sp | |
615 | .LP | |
616 | .B "DIRECTORY TOO SHORT I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
617 | .br | |
618 | A directory \fIF\fP has been found whose size \fIS\fP | |
619 | is less than the minimum size directory. | |
620 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP, | |
621 | and directory name \fIF\fP are printed. | |
622 | .LP | |
623 | Possible responses to the FIX prompt are: | |
624 | .IP YES | |
625 | increase the size of the directory to the minimum directory size. | |
626 | .IP NO | |
627 | ignore this directory. | |
628 | .sp | |
629 | .LP | |
630 | .B "DIRECTORY CORRUPTED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (SALVAGE)" | |
631 | .br | |
632 | A directory with an inconsistent internal state has been found. | |
633 | .LP | |
634 | Possible responses to the FIX prompt are: | |
635 | .IP YES | |
636 | throw away all entries up to the next 512-byte boundary. | |
637 | This rather drastic action can throw away up to 42 entries, | |
638 | and should be taken only after other recovery efforts have failed. | |
639 | .IP NO | |
640 | Skip up to the next 512-byte boundary and resume reading, | |
641 | but do not modify the directory. | |
642 | .sp | |
643 | .LP | |
644 | .B "BAD INODE NUMBER FOR `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
645 | .br | |
646 | A directory \fII\fP has been found whose inode number for `.' does | |
647 | does not equal \fII\fP. | |
648 | .LP | |
649 | Possible responses to the FIX prompt are: | |
650 | .IP YES | |
651 | change the inode number for `.' to be equal to \fII\fP. | |
652 | .IP NO | |
653 | leave the inode number for `.' unchanged. | |
654 | .sp | |
655 | .LP | |
656 | .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
657 | .br | |
658 | A directory \fII\fP has been found whose first entry is unallocated. | |
659 | .LP | |
660 | Possible responses to the FIX prompt are: | |
661 | .IP YES | |
662 | make an entry for `.' with inode number equal to \fII\fP. | |
663 | .IP NO | |
664 | leave the directory unchanged. | |
665 | .sp | |
666 | .LP | |
667 | .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" | |
668 | .br | |
669 | .B "CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS \fIF\fP" | |
670 | .br | |
671 | A directory \fII\fP has been found whose first entry is \fIF\fP. | |
672 | .I Fsck | |
673 | cannot resolve this problem. | |
674 | The file system should be mounted and the offending entry \fIF\fP | |
675 | moved elsewhere. | |
676 | The file system should then be unmounted and | |
677 | .I fsck | |
678 | should be run again. | |
679 | .sp | |
680 | .LP | |
681 | .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" | |
682 | .br | |
683 | .B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `.'" | |
684 | .br | |
685 | A directory \fII\fP has been found whose first entry is not `.'. | |
686 | .I Fsck | |
687 | cannot resolve this problem as it should never happen. | |
688 | See a guru. | |
689 | .sp | |
690 | .LP | |
691 | .B "EXTRA `.' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
692 | .br | |
693 | A directory \fII\fP has been found that has more than one entry for `.'. | |
694 | .LP | |
695 | Possible responses to the FIX prompt are: | |
696 | .IP YES | |
697 | remove the extra entry for `.'. | |
698 | .IP NO | |
699 | leave the directory unchanged. | |
700 | .sp | |
701 | .LP | |
702 | .B "BAD INODE NUMBER FOR `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
703 | .br | |
704 | A directory \fII\fP has been found whose inode number for `..' does | |
705 | does not equal the parent of \fII\fP. | |
706 | .LP | |
707 | Possible responses to the FIX prompt are: | |
708 | .IP YES | |
709 | change the inode number for `..' to be equal to the parent of \fII\fP. | |
710 | .IP NO | |
711 | leave the inode number for `..' unchanged. | |
712 | .sp | |
713 | .LP | |
714 | .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
715 | .br | |
716 | A directory \fII\fP has been found whose second entry is unallocated. | |
717 | .LP | |
718 | Possible responses to the FIX prompt are: | |
719 | .IP YES | |
720 | make an entry for `..' with inode number equal to the parent of \fII\fP. | |
721 | .IP NO | |
722 | leave the directory unchanged. | |
723 | .sp | |
724 | .LP | |
725 | .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" | |
726 | .br | |
727 | .B "CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS \fIF\fP" | |
728 | .br | |
729 | A directory \fII\fP has been found whose second entry is \fIF\fP. | |
730 | .I Fsck | |
731 | cannot resolve this problem. | |
732 | The file system should be mounted and the offending entry \fIF\fP | |
733 | moved elsewhere. | |
734 | The file system should then be unmounted and | |
735 | .I fsck | |
736 | should be run again. | |
737 | .sp | |
738 | .LP | |
739 | .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" | |
740 | .br | |
741 | .B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `..'" | |
742 | .br | |
743 | A directory \fII\fP has been found whose second entry is not `..'. | |
744 | .I Fsck | |
745 | cannot resolve this problem as it should never happen. | |
746 | See a guru. | |
747 | .sp | |
748 | .LP | |
749 | .B "EXTRA `..' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" | |
750 | .br | |
751 | A directory \fII\fP has been found that has more than one entry for `..'. | |
752 | .LP | |
753 | Possible responses to the FIX prompt are: | |
754 | .IP YES | |
755 | remove the extra entry for `..'. | |
756 | .IP NO | |
757 | leave the directory unchanged. | |
758 | .NH 2 | |
759 | Phase 3 \- Check Connectivity | |
760 | .PP | |
761 | This phase concerns itself with the directory connectivity seen in | |
762 | Phase 2. | |
763 | This section lists error conditions resulting from | |
764 | unreferenced directories, | |
765 | and missing or full | |
766 | .I lost+found | |
767 | directories. | |
768 | .sp | |
769 | .LP | |
770 | .B "UNREF DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)" | |
771 | .br | |
772 | The directory inode \fII\fP was not connected to a directory entry | |
773 | when the file system was traversed. | |
774 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP of directory | |
775 | inode \fII\fP are printed. | |
776 | When preen'ing, the directory is reconnected if its size is non-zero, | |
777 | otherwise it is cleared. | |
778 | .LP | |
779 | Possible responses to the RECONNECT prompt are: | |
780 | .IP YES | |
781 | reconnect directory inode \fII\fP to the file system in the | |
782 | directory for lost files (usually \fIlost+found\fP). | |
783 | This may invoke the | |
784 | .I lost+found | |
785 | error condition in Phase 3 | |
786 | if there are problems connecting directory inode \fII\fP to \fIlost+found\fP. | |
787 | This may also invoke the CONNECTED error condition in Phase 3 if the link | |
788 | was successful. | |
789 | .IP NO | |
790 | ignore this error condition. | |
791 | This will always invoke the UNREF error condition in Phase 4. | |
792 | .sp | |
793 | .LP | |
794 | .B "SORRY. NO lost+found DIRECTORY" | |
795 | .br | |
796 | There is no | |
797 | .I lost+found | |
798 | directory in the root directory of the file system; | |
799 | .I fsck | |
800 | ignores the request to link a directory in | |
801 | .I lost+found . | |
802 | This will always invoke the UNREF error condition in Phase 4. | |
803 | Check access modes of | |
804 | .I lost+found . | |
805 | See | |
806 | .I fsck (8) | |
807 | manual entry | |
808 | for further detail. | |
809 | This error is fatal if the file system is being preen'ed. | |
810 | .sp | |
811 | .LP | |
812 | .B "SORRY. NO SPACE IN lost+found DIRECTORY" | |
813 | .br | |
814 | There is no space to add another entry to the | |
815 | .I lost+found | |
816 | directory in the root directory | |
817 | of the file system; | |
818 | .I fsck | |
819 | ignores the request to link a directory in \fIlost+found\fP. | |
820 | This will always invoke the UNREF error condition in Phase 4. | |
821 | Clean out unnecessary entries in | |
822 | .I lost+found | |
823 | or make | |
824 | .I lost+found | |
825 | larger. | |
826 | See | |
827 | .I fsck (8) | |
828 | manual entry for further detail. | |
829 | This error is fatal if the file system is being preen'ed. | |
830 | .sp | |
831 | .LP | |
832 | .B "DIR I=\fII1\fP CONNECTED. PARENT WAS I=\fII2\fP" | |
833 | .br | |
834 | This is an advisory message indicating a directory inode \fII1\fP was | |
835 | successfully connected to the | |
836 | .I lost+found | |
837 | directory. | |
838 | The parent inode \fII2\fP of the directory inode \fII1\fP is | |
839 | replaced by the inode number of the | |
840 | .I lost+found | |
841 | directory. | |
842 | .NH 2 | |
843 | Phase 4 \- Check Reference Counts | |
844 | .PP | |
845 | This phase concerns itself with the link count information | |
846 | seen in Phase 2 and Phase 3. | |
847 | This section lists error conditions resulting from | |
848 | unreferenced files, | |
849 | missing or full | |
850 | .I lost+found | |
851 | directory, | |
852 | incorrect link counts for files, directories, symbolic links, or special files, | |
853 | unreferenced files, symbolic links, and directories, | |
854 | bad and duplicate blocks in files, symbolic links, and directories, | |
855 | and incorrect total free-inode counts. | |
856 | All errors in this phase are correctable if the file system is being preen'ed | |
857 | except running out of space in the lost+found directory. | |
858 | .sp | |
859 | .LP | |
860 | .B "UNREF FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)" | |
861 | .br | |
862 | Inode \fII\fP was not connected to a directory entry | |
863 | when the file system was traversed. | |
864 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and | |
865 | modify time \fIT\fP of inode \fII\fP are printed. | |
866 | When preen'ing the file is cleared if either its size or its | |
867 | link count is zero, | |
868 | otherwise it is reconnected. | |
869 | .LP | |
870 | Possible responses to the RECONNECT prompt are: | |
871 | .IP YES | |
872 | reconnect inode \fII\fP to the file system in the directory for | |
873 | lost files (usually \fIlost+found\fP). | |
874 | This may invoke the | |
875 | .I lost+found | |
876 | error condition in Phase 4 | |
877 | if there are problems connecting inode \fII\fP to | |
878 | .I lost+found. | |
879 | .IP NO | |
880 | ignore this error condition. | |
881 | This will always invoke the CLEAR error condition in Phase 4. | |
882 | .sp | |
883 | .LP | |
884 | .B "(CLEAR)" | |
885 | .br | |
886 | The inode mentioned in the immediately previous error condition can not be | |
887 | reconnected. | |
888 | This cannot occur if the file system is being preen'ed, | |
889 | since lack of space to reconnect files is a fatal error. | |
890 | .LP | |
891 | Possible responses to the CLEAR prompt are: | |
892 | .IP YES | |
893 | de-allocate the inode mentioned in the immediately previous error condition by zeroing its contents. | |
894 | .IP NO | |
895 | ignore this error condition. | |
896 | .sp | |
897 | .LP | |
898 | .B "SORRY. NO lost+found DIRECTORY" | |
899 | .br | |
900 | There is no | |
901 | .I lost+found | |
902 | directory in the root directory of the file system; | |
903 | .I fsck | |
904 | ignores the request to link a file in | |
905 | .I lost+found. | |
906 | This will always invoke the CLEAR error condition in Phase 4. | |
907 | Check access modes of | |
908 | .I lost+found . | |
909 | This error is fatal if the file system is being preen'ed. | |
910 | .sp | |
911 | .LP | |
912 | .B "SORRY. NO SPACE IN lost+found DIRECTORY" | |
913 | .br | |
914 | There is no space to add another entry to the | |
915 | .I lost+found | |
916 | directory in the root directory of the | |
917 | file system; | |
918 | .I fsck | |
919 | ignores the request to link a file in | |
920 | .I lost+found. | |
921 | This will always invoke the CLEAR error condition in Phase 4. | |
922 | Check size and contents of | |
923 | .I lost+found. | |
924 | This error is fatal if the file system is being preen'ed. | |
925 | .sp | |
926 | .LP | |
927 | .B "LINK COUNT FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP COUNT=\fIX\fP SHOULD BE \fIY\fP (ADJUST)" | |
928 | .br | |
929 | The link count for inode \fII\fP which is a file, | |
930 | is \fIX\fP but should be \fIY\fP. | |
931 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP | |
932 | are printed. | |
933 | When preen'ing the link count is adjusted. | |
934 | .LP | |
935 | Possible responses to the ADJUST prompt are: | |
936 | .IP YES | |
937 | replace the link count of file inode \fII\fP with \fIY\fP. | |
938 | .IP NO | |
939 | ignore this error condition. | |
940 | .sp | |
941 | .LP | |
942 | .B "LINK COUNT DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP COUNT=\fIX\fP SHOULD BE \fIY\fP (ADJUST)" | |
943 | .br | |
944 | The link count for inode \fII\fP which is a directory, | |
945 | is \fIX\fP but should be \fIY\fP. | |
946 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP | |
947 | of directory inode \fII\fP are printed. | |
948 | When preen'ing the link count is adjusted. | |
949 | .LP | |
950 | Possible responses to the ADJUST prompt are: | |
951 | .IP YES | |
952 | replace the link count of directory inode \fII\fP with \fIY\fP. | |
953 | .IP NO | |
954 | ignore this error condition. | |
955 | .sp | |
956 | .LP | |
957 | .B "LINK COUNT \fIF\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP COUNT=\fIX\fP SHOULD BE \fIY\fP (ADJUST)" | |
958 | .br | |
959 | The link count for \fIF\fP inode \fII\fP is \fIX\fP but should be \fIY\fP. | |
960 | The name \fIF\fP, | |
961 | owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time | |
962 | \fIT\fP | |
963 | are printed. | |
964 | When preen'ing the link count is adjusted. | |
965 | .LP | |
966 | Possible responses to the ADJUST prompt are: | |
967 | .IP YES | |
968 | replace the link count of inode \fII\fP with \fIY\fP. | |
969 | .IP NO | |
970 | ignore this error condition. | |
971 | .sp | |
972 | .LP | |
973 | .B "UNREF FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)" | |
974 | .br | |
975 | Inode \fII\fP which is a file, was not connected to a directory entry when the | |
976 | file system was traversed. | |
977 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, | |
978 | and modify time \fIT\fP of inode \fII\fP | |
979 | are printed. | |
980 | When preen'ing, | |
981 | this is a file that was not connected because its size or link count was zero, | |
982 | hence it is cleared. | |
983 | .LP | |
984 | Possible responses to the CLEAR prompt are: | |
985 | .IP YES | |
986 | de-allocate inode \fII\fP by zeroing its contents. | |
987 | .IP NO | |
988 | ignore this error condition. | |
989 | .sp | |
990 | .LP | |
991 | .B "UNREF DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)" | |
992 | .br | |
993 | Inode \fII\fP which is a directory, | |
994 | was not connected to a directory entry when the | |
995 | file system was traversed. | |
996 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, | |
997 | and modify time \fIT\fP of inode \fII\fP | |
998 | are printed. | |
999 | When preen'ing, | |
1000 | this is a directory that was not connected | |
1001 | because its size or link count was zero, | |
1002 | hence it is cleared. | |
1003 | .LP | |
1004 | Possible responses to the CLEAR prompt are: | |
1005 | .IP YES | |
1006 | de-allocate inode \fII\fP by zeroing its contents. | |
1007 | .IP NO | |
1008 | ignore this error condition. | |
1009 | .sp | |
1010 | .LP | |
1011 | .B "BAD/DUP FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)" | |
1012 | .br | |
1013 | Phase 1 or Phase 1b have found duplicate blocks | |
1014 | or bad blocks associated with | |
1015 | file inode \fII\fP. | |
1016 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, | |
1017 | and modify time \fIT\fP of inode \fII\fP | |
1018 | are printed. | |
1019 | This error cannot arise when the file system is being preen'ed, | |
1020 | as it would have caused a fatal error earlier. | |
1021 | .LP | |
1022 | Possible responses to the CLEAR prompt are: | |
1023 | .IP YES | |
1024 | de-allocate inode \fII\fP by zeroing its contents. | |
1025 | .IP NO | |
1026 | ignore this error condition. | |
1027 | .sp | |
1028 | .LP | |
1029 | .B "BAD/DUP DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)" | |
1030 | .br | |
1031 | Phase 1 or Phase 1b have found duplicate blocks or | |
1032 | bad blocks associated with directory inode \fII\fP. | |
1033 | The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, | |
1034 | and modify time \fIT\fP of inode \fII\fP | |
1035 | are printed. | |
1036 | This error cannot arise when the file system is being preen'ed, | |
1037 | as it would have caused a fatal error earlier. | |
1038 | .LP | |
1039 | Possible responses to the CLEAR prompt are: | |
1040 | .IP YES | |
1041 | de-allocate inode \fII\fP by zeroing its contents. | |
1042 | .IP NO | |
1043 | ignore this error condition. | |
1044 | .sp | |
1045 | .LP | |
1046 | .B "FREE INODE COUNT WRONG IN SUPERBLK (FIX)" | |
1047 | .br | |
1048 | The actual count of the free inodes does not | |
1049 | match the count in the super-block | |
1050 | of the file system. | |
1051 | When preen'ing, | |
1052 | the count is fixed. | |
1053 | .LP | |
1054 | Possible responses to the FIX prompt are: | |
1055 | .IP YES | |
1056 | replace the count in the super-block by the actual count. | |
1057 | .IP NO | |
1058 | ignore this error condition. | |
1059 | .NH 2 | |
1060 | Phase 5 - Check Cyl groups | |
1061 | .PP | |
1062 | This phase concerns itself with the free-block maps. | |
1063 | This section lists error conditions resulting from | |
1064 | allocated blocks in the free-block maps, | |
1065 | free blocks missing from free-block maps, | |
1066 | and the total free-block count incorrect. | |
1067 | .sp | |
1068 | .LP | |
1069 | .B "CG \fIC\fP: BAD MAGIC NUMBER" | |
1070 | .br | |
1071 | The magic number of cylinder group \fIC\fP is wrong. | |
1072 | This usually indicates that the cylinder group maps have been destroyed. | |
1073 | When running manually the cylinder group is marked as needing | |
1074 | to be reconstructed. | |
1075 | This error is fatal if the file system is being preen'ed. | |
1076 | .sp | |
1077 | .LP | |
1078 | .B "EXCESSIVE BAD BLKS IN BIT MAPS (CONTINUE)" | |
1079 | .br | |
1080 | An inode contains | |
1081 | more than a tolerable number (usually 10) of blocks | |
1082 | claimed by other inodes or that are out of the legal range | |
1083 | for the file system. | |
1084 | This error is fatal if the file system is being preen'ed. | |
1085 | .LP | |
1086 | Possible responses to the CONTINUE prompt are: | |
1087 | .IP YES | |
1088 | ignore the rest of the free-block maps and continue the execution of | |
1089 | .I fsck. | |
1090 | .IP NO | |
1091 | terminate the program. | |
1092 | .sp | |
1093 | .LP | |
1094 | .B "SUMMARY INFORMATION \fIT\fP BAD" | |
1095 | .br | |
1096 | where \fIT\fP is one or more of: | |
1097 | .br | |
1098 | .B "(INODE FREE)" | |
1099 | .br | |
1100 | .B "(BLOCK OFFSETS)" | |
1101 | .br | |
1102 | .B "(FRAG SUMMARIES)" | |
1103 | .br | |
1104 | .B "(SUPER BLOCK SUMMARIES)" | |
1105 | .br | |
1106 | The indicated summary information was found to be incorrect. | |
1107 | This error condition will always invoke the | |
1108 | .B "BAD CYLINDER GROUPS" | |
1109 | condition in Phase 6. | |
1110 | When preen'ing, | |
1111 | the summary information is recomputed. | |
1112 | .sp | |
1113 | .LP | |
1114 | .B "\fIX\fP BLK(S) MISSING" | |
1115 | .br | |
1116 | \fIX\fP blocks | |
1117 | unused by the file system were not found in the free-block maps. | |
1118 | This error condition will always invoke the | |
1119 | .B "BAD CYLINDER GROUPS" | |
1120 | condition in Phase 6. | |
1121 | When preen'ing, | |
1122 | the block maps are rebuilt. | |
1123 | .sp | |
1124 | .LP | |
1125 | .B "BAD CYLINDER GROUPS (SALVAGE)" | |
1126 | .br | |
1127 | Phase 5 has found | |
1128 | bad blocks in the free-block maps, | |
1129 | duplicate blocks in the free-block maps, | |
1130 | or blocks missing from the file system. | |
1131 | When preen'ing, | |
1132 | the cylinder groups are reconstructed. | |
1133 | .LP | |
1134 | Possible responses to the SALVAGE prompt are: | |
1135 | .IP YES | |
1136 | replace the actual free-block maps with a new free-block maps. | |
1137 | .IP NO | |
1138 | ignore this error condition. | |
1139 | .sp | |
1140 | .LP | |
1141 | .B "FREE BLK COUNT WRONG IN SUPERBLOCK (FIX)" | |
1142 | .br | |
1143 | The actual count of free blocks does not match the count in the | |
1144 | super-block of the file system. | |
1145 | When preen'ing, | |
1146 | the counts are fixed. | |
1147 | .LP | |
1148 | Possible responses to the FIX prompt are: | |
1149 | .IP YES | |
1150 | replace the count in the super-block by the actual count. | |
1151 | .IP NO | |
1152 | ignore this error condition. | |
1153 | .NH 2 | |
1154 | Phase 6 - Salvage Cylinder Groups | |
1155 | .PP | |
1156 | This phase concerns itself with the free-block maps reconstruction. | |
1157 | No error messages are produced. | |
1158 | .NH 2 | |
1159 | Cleanup | |
1160 | .PP | |
1161 | Once a file system has been checked, a few cleanup functions are performed. | |
1162 | This section lists advisory messages about | |
1163 | the file system | |
1164 | and modify status of the file system. | |
1165 | .sp | |
1166 | .LP | |
1167 | .B "\fIV\fP files, \fIW\fP used, \fIX\fP free (\fIY\fP frags, \fIZ\fP blocks)" | |
1168 | .br | |
1169 | This is an advisory message indicating that | |
1170 | the file system checked contained | |
1171 | \fIV\fP files using | |
1172 | \fIW\fP fragment sized blocks leaving | |
1173 | \fIX\fP fragment sized blocks free in the file system. | |
1174 | The numbers in parenthesis breaks the free count down into | |
1175 | \fIY\fP free fragments and | |
1176 | \fIZ\fP free full sized blocks. | |
1177 | .sp | |
1178 | .LP | |
1179 | .B "***** REBOOT UNIX *****" | |
1180 | .br | |
1181 | This is an advisory message indicating that | |
1182 | the root file system has been modified by | |
1183 | .I fsck. | |
1184 | If UNIX is not rebooted immediately, | |
1185 | the work done by | |
1186 | .I fsck | |
1187 | may be undone by the in-core copies of tables | |
1188 | UNIX keeps. | |
1189 | When preen'ing, | |
1190 | .I fsck | |
1191 | will exit with a code of 4. | |
1192 | The auto-reboot script interprets an exit code of 4 | |
1193 | by issuing a reboot system call. | |
1194 | .sp | |
1195 | .LP | |
1196 | .B "***** FILE SYSTEM WAS MODIFIED *****" | |
1197 | .br | |
1198 | This is an advisory message indicating that | |
1199 | the current file system was modified by | |
1200 | .I fsck. | |
1201 | If this file system is mounted or is the current root file system, | |
1202 | .I fsck | |
1203 | should be halted and UNIX rebooted. | |
1204 | If UNIX is not rebooted immediately, | |
1205 | the work done by | |
1206 | .I fsck | |
1207 | may be undone by the in-core copies of tables | |
1208 | UNIX keeps. |