| blob | a479992ee8dbbe0165b58eeed4603557be0ed6c2 |
1 .\" $NetBSD: 4.t,v 1.4 2001/11/21 19:14:25 wiz Exp $
2 .\"
3 .\" Copyright (c) 1982, 1993
4 .\" The Regents of the University of California. All rights reserved.
5 .\"
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
8 .\" are met:
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
17 .\"
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" SUCH DAMAGE.
29 .\"
30 .\" @(#)4.t 8.1 (Berkeley) 6/5/93
31 .\"
32 .ds RH Appendix A \- Fsck_ffs Error Conditions
33 .NH
34 Appendix A \- Fsck_ffs Error Conditions
35 .NH 2
36 Conventions
37 .PP
38 .I Fsck_ffs
39 is
40 a multi-pass file system check program.
41 Each file system pass invokes a different Phase of the
42 .I fsck_ffs
43 program.
44 After the initial setup,
45 .I fsck_ffs
46 performs successive Phases over each file system,
47 checking blocks and sizes,
48 path-names,
49 connectivity,
50 reference counts,
51 and the map of free blocks,
52 (possibly rebuilding it),
53 and performs some cleanup.
54 .LP
55 Normally
56 .I fsck_ffs
57 is run non-interactively to
58 .I preen
59 the file systems after an unclean halt.
60 While preen'ing a file system,
61 it will only fix corruptions that are expected
62 to occur from an unclean halt.
63 These actions are a proper subset of the actions that
64 .I fsck_ffs
65 will take when it is running interactively.
66 Throughout this appendix many errors have several options
67 that the operator can take.
68 When an inconsistency is detected,
69 .I fsck_ffs
70 reports the error condition to the operator.
71 If a response is required,
72 .I fsck_ffs
73 prints a prompt message and
74 waits for a response.
75 When preen'ing most errors are fatal.
76 For those that are expected,
77 the response taken is noted.
78 This appendix explains the meaning of each error condition,
79 the possible responses, and the related error conditions.
80 .LP
81 The error conditions are organized by the
82 .I Phase
83 of the
84 .I fsck_ffs
85 program in which they can occur.
86 The error conditions that may occur
87 in more than one Phase
88 will be discussed in initialization.
89 .NH 2
90 Initialization
91 .PP
92 Before a file system check can be performed, certain
93 tables have to be set up and certain files opened.
94 This section concerns itself with the opening of files and
95 the initialization of tables.
96 This section lists error conditions resulting from
97 command line options,
98 memory requests,
99 opening of files,
100 status of files,
101 file system size checks,
102 and creation of the scratch file.
103 All the initialization errors are fatal
104 when the file system is being preen'ed.
105 .sp
106 .LP
107 .B "\fIC\fP option?"
108 .br
109 \fIC\fP is not a legal option to
110 .I fsck_ffs ;
111 legal options are \-b, \-c, \-y, \-n, and \-p.
112 .I Fsck_ffs
113 terminates on this error condition.
114 See the
115 .I fsck_ffs (8)
116 manual entry for further detail.
117 .sp
118 .LP
119 .B "cannot alloc NNN bytes for blockmap"
120 .br
121 .B "cannot alloc NNN bytes for freemap"
122 .br
123 .B "cannot alloc NNN bytes for statemap"
124 .br
125 .B "cannot alloc NNN bytes for lncntp"
126 .br
127 .I Fsck_ffs 's
128 request for memory for its virtual
129 memory tables failed.
130 This should never happen.
131 .I Fsck_ffs
132 terminates on this error condition.
133 See a guru.
134 .sp
135 .LP
136 .B "Can't open checklist file: \fIF\fP"
137 .br
138 The file system checklist file
139 \fIF\fP (usually
140 .I /etc/fstab )
141 can not be opened for reading.
142 .I Fsck_ffs
143 terminates on this error condition.
144 Check access modes of \fIF\fP.
145 .sp
146 .LP
147 .B "Can't stat root"
148 .br
149 .I Fsck_ffs 's
150 request for statistics about the root directory ``/'' failed.
151 This should never happen.
152 .I Fsck_ffs
153 terminates on this error condition.
154 See a guru.
155 .sp
156 .LP
157 .B "Can't stat \fIF\fP"
158 .br
159 .B "Can't make sense out of name \fIF\fP"
160 .br
161 .I Fsck_ffs 's
162 request for statistics about the file system \fIF\fP failed.
163 When running manually,
164 it ignores this file system
165 and continues checking the next file system given.
166 Check access modes of \fIF\fP.
167 .sp
168 .LP
169 .B "Can't open \fIF\fP"
170 .br
171 .I Fsck_ffs 's
172 request attempt to open the file system \fIF\fP failed.
173 When running manually, it ignores this file system
174 and continues checking the next file system given.
175 Check access modes of \fIF\fP.
176 .sp
177 .LP
178 .B "\fIF\fP: (NO WRITE)"
179 .br
180 Either the \-n flag was specified or
181 .I fsck_ffs 's
182 attempt to open the file system \fIF\fP for writing failed.
183 When running manually,
184 all the diagnostics are printed out,
185 but no modifications are attempted to fix them.
186 .sp
187 .LP
188 .B "file is not a block or character device; OK"
189 .br
190 You have given
191 .I fsck_ffs
192 a regular file name by mistake.
193 Check the type of the file specified.
194 .LP
195 Possible responses to the OK prompt are:
196 .IP YES
197 ignore this error condition.
198 .IP NO
199 ignore this file system and continues checking
200 the next file system given.
201 .sp
202 .LP
203 .B "UNDEFINED OPTIMIZATION IN SUPERBLOCK (SET TO DEFAULT)"
204 .br
205 The superblock optimization parameter is neither OPT_TIME
206 nor OPT_SPACE.
207 .LP
208 Possible responses to the SET TO DEFAULT prompt are:
209 .IP YES
210 The superblock is set to request optimization to minimize
211 running time of the system.
212 (If optimization to minimize disk space utilization is
213 desired, it can be set using \fItunefs\fP(8).)
214 .IP NO
215 ignore this error condition.
216 .sp
217 .LP
218 .B "IMPOSSIBLE MINFREE=\fID\fP IN SUPERBLOCK (SET TO DEFAULT)"
219 .br
220 The superblock minimum space percentage is greater than 99%
221 or less than 0%.
222 .LP
223 Possible responses to the SET TO DEFAULT prompt are:
224 .IP YES
225 The minfree parameter is set to 10%.
226 (If some other percentage is desired,
227 it can be set using \fItunefs\fP(8).)
228 .IP NO
229 ignore this error condition.
230 .sp
231 .LP
232 .B "IMPOSSIBLE INTERLEAVE=\fID\fP IN SUPERBLOCK (SET TO DEFAULT)"
233 .br
234 The file system interleave is less than or equal to zero.
235 .LP
236 Possible responses to the SET TO DEFAULT prompt are:
237 .IP YES
238 The interleave parameter is set to 1.
239 .IP NO
240 ignore this error condition.
241 .sp
242 .LP
243 .B "IMPOSSIBLE NPSECT=\fID\fP IN SUPERBLOCK (SET TO DEFAULT)"
244 .br
245 The number of physical sectors per track is less than the number
246 of usable sectors per track.
247 .LP
248 Possible responses to the SET TO DEFAULT prompt are:
249 .IP YES
250 The npsect parameter is set to the number of usable sectors per track.
251 .IP NO
252 ignore this error condition.
253 .sp
254 .LP
255 One of the following messages will appear:
256 .br
257 .B "MAGIC NUMBER WRONG"
258 .br
259 .B "NCG OUT OF RANGE"
260 .br
261 .B "CPG OUT OF RANGE"
262 .br
263 .B "NCYL DOES NOT JIVE WITH NCG*CPG"
264 .br
265 .B "SIZE PREPOSTEROUSLY LARGE"
266 .br
267 .B "TRASHED VALUES IN SUPER BLOCK"
268 .br
269 and will be followed by the message:
270 .br
271 .B "\fIF\fP: BAD SUPER BLOCK: \fIB\fP"
272 .br
273 .B "USE -b OPTION TO FSCK_FFS TO SPECIFY LOCATION OF AN ALTERNATE"
274 .br
275 .B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck_ffs(8)."
276 .br
277 The super block has been corrupted.
278 An alternative super block must be selected from among those
279 listed by
280 .I newfs
281 (8) when the file system was created.
282 For file systems with a blocksize less than 32K,
283 specifying \-b 32 is a good first choice.
284 .sp
285 .LP
286 .B "INTERNAL INCONSISTENCY: \fIM\fP"
287 .br
288 .I Fsck_ffs 's
289 has had an internal panic, whose message is specified as \fIM\fP.
290 This should never happen.
291 See a guru.
292 .sp
293 .LP
294 .B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)"
295 .br
296 .I Fsck_ffs 's
297 request for moving to a specified block number \fIB\fP in
298 the file system failed.
299 This should never happen.
300 See a guru.
301 .LP
302 Possible responses to the CONTINUE prompt are:
303 .IP YES
304 attempt to continue to run the file system check.
305 Often,
306 however the problem will persist.
307 This error condition will not allow a complete check of the file system.
308 A second run of
309 .I fsck_ffs
310 should be made to re-check this file system.
311 If the block was part of the virtual memory buffer
312 cache,
313 .I fsck_ffs
314 will terminate with the message ``Fatal I/O error''.
315 .IP NO
316 terminate the program.
317 .sp
318 .LP
319 .B "CAN NOT READ: BLK \fIB\fP (CONTINUE)"
320 .br
321 .I Fsck_ffs 's
322 request for reading a specified block number \fIB\fP in
323 the file system failed.
324 This should never happen.
325 See a guru.
326 .LP
327 Possible responses to the CONTINUE prompt are:
328 .IP YES
329 attempt to continue to run the file system check.
330 It will retry the read and print out the message:
331 .br
332 .B "THE FOLLOWING SECTORS COULD NOT BE READ: \fIN\fP"
333 .br
334 where \fIN\fP indicates the sectors that could not be read.
335 If
336 .I fsck_ffs
337 ever tries to write back one of the blocks on which the read failed
338 it will print the message:
339 .br
340 .B "WRITING ZERO'ED BLOCK \fIN\fP TO DISK"
341 .br
342 where \fIN\fP indicates the sector that was written with zero's.
343 If the disk is experiencing hardware problems, the problem will persist.
344 This error condition will not allow a complete check of the file system.
345 A second run of
346 .I fsck_ffs
347 should be made to re-check this file system.
348 If the block was part of the virtual memory buffer
349 cache,
350 .I fsck_ffs
351 will terminate with the message ``Fatal I/O error''.
352 .IP NO
353 terminate the program.
354 .sp
355 .LP
356 .B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)"
357 .br
358 .I Fsck_ffs 's
359 request for writing a specified block number \fIB\fP
360 in the file system failed.
361 The disk is write-protected;
362 check the write protect lock on the drive.
363 If that is not the problem, see a guru.
364 .LP
365 Possible responses to the CONTINUE prompt are:
366 .IP YES
367 attempt to continue to run the file system check.
368 The write operation will be retried with the failed blocks
369 indicated by the message:
370 .br
371 .B "THE FOLLOWING SECTORS COULD NOT BE WRITTEN: \fIN\fP"
372 .br
373 where \fIN\fP indicates the sectors that could not be written.
374 If the disk is experiencing hardware problems, the problem will persist.
375 This error condition will not allow a complete check of the file system.
376 A second run of
377 .I fsck_ffs
378 should be made to re-check this file system.
379 If the block was part of the virtual memory buffer
380 cache,
381 .I fsck_ffs
382 will terminate with the message ``Fatal I/O error''.
383 .IP NO
384 terminate the program.
385 .sp
386 .LP
387 .B "bad inode number DDD to ginode"
388 .br
389 An internal error has attempted to read non-existent inode \fIDDD\fP.
390 This error causes
391 .I fsck_ffs
392 to exit.
393 See a guru.
394 .NH 2
395 Phase 1 \- Check Blocks and Sizes
396 .PP
397 This phase concerns itself with
398 the inode list.
399 This section lists error conditions resulting from
400 checking inode types,
401 setting up the zero-link-count table,
402 examining inode block numbers for bad or duplicate blocks,
403 checking inode size,
404 and checking inode format.
405 All errors in this phase except
406 .B "INCORRECT BLOCK COUNT"
407 and
408 .B "PARTIALLY TRUNCATED INODE"
409 are fatal if the file system is being preen'ed.
410 .sp
411 .LP
412 .B "UNKNOWN FILE TYPE I=\fII\fP (CLEAR)"
413 .br
414 The mode word of the inode \fII\fP indicates that the inode is not a
415 special block inode, special character inode, socket inode, regular inode,
416 symbolic link, or directory inode.
417 .LP
418 Possible responses to the CLEAR prompt are:
419 .IP YES
420 de-allocate inode \fII\fP by zeroing its contents.
421 This will always invoke the UNALLOCATED error condition in Phase 2
422 for each directory entry pointing to this inode.
423 .IP NO
424 ignore this error condition.
425 .sp
426 .LP
427 .B "PARTIALLY TRUNCATED INODE I=\fII\fP (SALVAGE)"
428 .br
429 .I Fsck_ffs
430 has found inode \fII\fP whose size is shorter than the number of
431 blocks allocated to it.
432 This condition should only occur if the system crashes while in the
433 midst of truncating a file.
434 When preen'ing the file system,
435 .I fsck_ffs
436 completes the truncation to the specified size.
437 .LP
438 Possible responses to SALVAGE are:
439 .IP YES
440 complete the truncation to the size specified in the inode.
441 .IP NO
442 ignore this error condition.
443 .sp
444 .LP
445 .B "LINK COUNT TABLE OVERFLOW (CONTINUE)"
446 .br
447 An internal table for
448 .I fsck_ffs
449 containing allocated inodes with a link count of
450 zero cannot allocate more memory.
451 Increase the virtual memory for
452 .I fsck_ffs .
453 .LP
454 Possible responses to the CONTINUE prompt are:
455 .IP YES
456 continue with the program.
457 This error condition will not allow a complete check of the file system.
458 A second run of
459 .I fsck_ffs
460 should be made to re-check this file system.
461 If another allocated inode with a zero link count is found,
462 this error condition is repeated.
463 .IP NO
464 terminate the program.
465 .sp
466 .LP
467 .B "\fIB\fP BAD I=\fII\fP"
468 .br
469 Inode \fII\fP contains block number \fIB\fP with a number
470 lower than the number of the first data block in the file system or
471 greater than the number of the last block
472 in the file system.
473 This error condition may invoke the
474 .B "EXCESSIVE BAD BLKS"
475 error condition in Phase 1 (see next paragraph) if
476 inode \fII\fP has too many block numbers outside the file system range.
477 This error condition will always invoke the
478 .B "BAD/DUP"
479 error condition in Phase 2 and Phase 4.
480 .sp
481 .LP
482 .B "EXCESSIVE BAD BLKS I=\fII\fP (CONTINUE)"
483 .br
484 There is more than a tolerable number (usually 10) of blocks with a number
485 lower than the number of the first data block in the file system or greater than
486 the number of last block in the file system associated with inode \fII\fP.
487 .LP
488 Possible responses to the CONTINUE prompt are:
489 .IP YES
490 ignore the rest of the blocks in this inode
491 and continue checking with the next inode in the file system.
492 This error condition will not allow a complete check of the file system.
493 A second run of
494 .I fsck_ffs
495 should be made to re-check this file system.
496 .IP NO
497 terminate the program.
498 .sp
499 .LP
500 .B "BAD STATE DDD TO BLKERR"
501 .br
502 An internal error has scrambled
503 .I fsck_ffs 's
504 state map to have the impossible value \fIDDD\fP.
505 .I Fsck_ffs
506 exits immediately.
507 See a guru.
508 .sp
509 .LP
510 .B "\fIB\fP DUP I=\fII\fP"
511 .br
512 Inode \fII\fP contains block number \fIB\fP that is already claimed by
513 another inode.
514 This error condition may invoke the
515 .B "EXCESSIVE DUP BLKS"
516 error condition in Phase 1 if
517 inode \fII\fP has too many block numbers claimed by other inodes.
518 This error condition will always invoke Phase 1b and the
519 .B "BAD/DUP"
520 error condition in Phase 2 and Phase 4.
521 .sp
522 .LP
523 .B "EXCESSIVE DUP BLKS I=\fII\fP (CONTINUE)"
524 .br
525 There is more than a tolerable number (usually 10) of blocks claimed by other
526 inodes.
527 .LP
528 Possible responses to the CONTINUE prompt are:
529 .IP YES
530 ignore the rest of the blocks in this inode
531 and continue checking with the next inode in the file system.
532 This error condition will not allow a complete check of the file system.
533 A second run of
534 .I fsck_ffs
535 should be made to re-check this file system.
536 .IP NO
537 terminate the program.
538 .sp
539 .LP
540 .B "DUP TABLE OVERFLOW (CONTINUE)"
541 .br
542 An internal table in
543 .I fsck_ffs
544 containing duplicate block numbers cannot allocate any more space.
545 Increase the amount of virtual memory available to
546 .I fsck_ffs .
547 .LP
548 Possible responses to the CONTINUE prompt are:
549 .IP YES
550 continue with the program.
551 This error condition will not allow a complete check of the file system.
552 A second run of
553 .I fsck_ffs
554 should be made to re-check this file system.
555 If another duplicate block is found, this error condition will repeat.
556 .IP NO
557 terminate the program.
558 .sp
559 .LP
560 .B "PARTIALLY ALLOCATED INODE I=\fII\fP (CLEAR)"
561 .br
562 Inode \fII\fP is neither allocated nor unallocated.
563 .LP
564 Possible responses to the CLEAR prompt are:
565 .IP YES
566 de-allocate inode \fII\fP by zeroing its contents.
567 .IP NO
568 ignore this error condition.
569 .sp
570 .LP
571 .B "INCORRECT BLOCK COUNT I=\fII\fP (\fIX\fP should be \fIY\fP) (CORRECT)"
572 .br
573 The block count for inode \fII\fP is \fIX\fP blocks,
574 but should be \fIY\fP blocks.
575 When preen'ing the count is corrected.
576 .LP
577 Possible responses to the CORRECT prompt are:
578 .IP YES
579 replace the block count of inode \fII\fP with \fIY\fP.
580 .IP NO
581 ignore this error condition.
582 .NH 2
583 Phase 1B: Rescan for More Dups
584 .PP
585 When a duplicate block is found in the file system, the file system is
586 rescanned to find the inode that previously claimed that block.
587 This section lists the error condition when the duplicate block is found.
588 .sp
589 .LP
590 .B "\fIB\fP DUP I=\fII\fP"
591 .br
592 Inode \fII\fP contains block number \fIB\fP that
593 is already claimed by another inode.
594 This error condition will always invoke the
595 .B "BAD/DUP"
596 error condition in Phase 2.
597 You can determine which inodes have overlapping blocks by examining
598 this error condition and the DUP error condition in Phase 1.
599 .NH 2
600 Phase 2 \- Check Pathnames
601 .PP
602 This phase concerns itself with removing directory entries
603 pointing to
604 error conditioned inodes
605 from Phase 1 and Phase 1b.
606 This section lists error conditions resulting from
607 root inode mode and status,
608 directory inode pointers in range,
609 and directory entries pointing to bad inodes,
610 and directory integrity checks.
611 All errors in this phase are fatal if the file system is being preen'ed,
612 except for directories not being a multiple of the blocks size
613 and extraneous hard links.
614 .sp
615 .LP
616 .B "ROOT INODE UNALLOCATED (ALLOCATE)"
617 .br
618 The root inode (usually inode number 2) has no allocate mode bits.
619 This should never happen.
620 .LP
621 Possible responses to the ALLOCATE prompt are:
622 .IP YES
623 allocate inode 2 as the root inode.
624 The files and directories usually found in the root will be recovered
625 in Phase 3 and put into
626 .I lost+found .
627 If the attempt to allocate the root fails,
628 .I fsck_ffs
629 will exit with the message:
630 .br
631 .B "CANNOT ALLOCATE ROOT INODE" .
632 .IP NO
633 .I fsck_ffs
634 will exit.
635 .sp
636 .LP
637 .B "ROOT INODE NOT DIRECTORY (REALLOCATE)"
638 .br
639 The root inode (usually inode number 2)
640 is not directory inode type.
641 .LP
642 Possible responses to the REALLOCATE prompt are:
643 .IP YES
644 clear the existing contents of the root inode
645 and reallocate it.
646 The files and directories usually found in the root will be recovered
647 in Phase 3 and put into
648 .I lost+found .
649 If the attempt to allocate the root fails,
650 .I fsck_ffs
651 will exit with the message:
652 .br
653 .B "CANNOT ALLOCATE ROOT INODE" .
654 .IP NO
655 .I fsck_ffs
656 will then prompt with
657 .B "FIX"
658 .LP
659 Possible responses to the FIX prompt are:
660 .IP YES
661 replace the root inode's type to be a directory.
662 If the root inode's data blocks are not directory blocks,
663 many error conditions will be produced.
664 .IP NO
665 terminate the program.
666 .sp
667 .LP
668 .B "DUPS/BAD IN ROOT INODE (REALLOCATE)"
669 .br
670 Phase 1 or Phase 1b have found duplicate blocks
671 or bad blocks in the root inode (usually inode number 2) for the file system.
672 .LP
673 Possible responses to the REALLOCATE prompt are:
674 .IP YES
675 clear the existing contents of the root inode
676 and reallocate it.
677 The files and directories usually found in the root will be recovered
678 in Phase 3 and put into
679 .I lost+found .
680 If the attempt to allocate the root fails,
681 .I fsck_ffs
682 will exit with the message:
683 .br
684 .B "CANNOT ALLOCATE ROOT INODE" .
685 .IP NO
686 .I fsck_ffs
687 will then prompt with
688 .B "CONTINUE" .
689 .LP
690 Possible responses to the CONTINUE prompt are:
691 .IP YES
692 ignore the
693 .B "DUPS/BAD"
694 error condition in the root inode and
695 attempt to continue to run the file system check.
696 If the root inode is not correct,
697 then this may result in many other error conditions.
698 .IP NO
699 terminate the program.
700 .sp
701 .LP
702 .B "NAME TOO LONG \fIF\fP"
703 .br
704 An excessively long path name has been found.
705 This usually indicates loops in the file system name space.
706 This can occur if the super user has made circular links to directories.
707 The offending links must be removed (by a guru).
708 .sp
709 .LP
710 .B "I OUT OF RANGE I=\fII\fP NAME=\fIF\fP (REMOVE)"
711 .br
712 A directory entry \fIF\fP has an inode number \fII\fP that is greater than
713 the end of the inode list.
714 .LP
715 Possible responses to the REMOVE prompt are:
716 .IP YES
717 the directory entry \fIF\fP is removed.
718 .IP NO
719 ignore this error condition.
720 .sp
721 .LP
722 .B "UNALLOCATED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP \fItype\fP=\fIF\fP (REMOVE)"
723 .br
724 A directory or file entry \fIF\fP points to an unallocated inode \fII\fP.
725 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP,
726 and name \fIF\fP are printed.
727 .LP
728 Possible responses to the REMOVE prompt are:
729 .IP YES
730 the directory entry \fIF\fP is removed.
731 .IP NO
732 ignore this error condition.
733 .sp
734 .LP
735 .B "DUP/BAD I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP \fItype\fP=\fIF\fP (REMOVE)"
736 .br
737 Phase 1 or Phase 1b have found duplicate blocks or bad blocks
738 associated with directory or file entry \fIF\fP, inode \fII\fP.
739 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP,
740 and directory name \fIF\fP are printed.
741 .LP
742 Possible responses to the REMOVE prompt are:
743 .IP YES
744 the directory entry \fIF\fP is removed.
745 .IP NO
746 ignore this error condition.
747 .sp
748 .LP
749 .B "ZERO LENGTH DIRECTORY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (REMOVE)"
750 .br
751 A directory entry \fIF\fP has a size \fIS\fP that is zero.
752 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP,
753 and directory name \fIF\fP are printed.
754 .LP
755 Possible responses to the REMOVE prompt are:
756 .IP YES
757 the directory entry \fIF\fP is removed;
758 this will always invoke the BAD/DUP error condition in Phase 4.
759 .IP NO
760 ignore this error condition.
761 .sp
762 .LP
763 .B "DIRECTORY TOO SHORT I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
764 .br
765 A directory \fIF\fP has been found whose size \fIS\fP
766 is less than the minimum size directory.
767 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, modify time \fIT\fP,
768 and directory name \fIF\fP are printed.
769 .LP
770 Possible responses to the FIX prompt are:
771 .IP YES
772 increase the size of the directory to the minimum directory size.
773 .IP NO
774 ignore this directory.
775 .sp
776 .LP
777 .B "DIRECTORY \fIF\fP LENGTH \fIS\fP NOT MULTIPLE OF \fIB\fP (ADJUST)
778 .br
779 A directory \fIF\fP has been found with size \fIS\fP that is not
780 a multiple of the directory blocksize \fIB\fP.
781 .LP
782 Possible responses to the ADJUST prompt are:
783 .IP YES
784 the length is rounded up to the appropriate block size.
785 This error can occur on 4.2BSD file systems.
786 Thus when preen'ing the file system only a warning is printed
787 and the directory is adjusted.
788 .IP NO
789 ignore the error condition.
790 .sp
791 .LP
792 .B "DIRECTORY CORRUPTED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (SALVAGE)"
793 .br
794 A directory with an inconsistent internal state has been found.
795 .LP
796 Possible responses to the FIX prompt are:
797 .IP YES
798 throw away all entries up to the next directory boundary (usually 512-byte)
799 boundary.
800 This drastic action can throw away up to 42 entries,
801 and should be taken only after other recovery efforts have failed.
802 .IP NO
803 skip up to the next directory boundary and resume reading,
804 but do not modify the directory.
805 .sp
806 .LP
807 .B "BAD INODE NUMBER FOR `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
808 .br
809 A directory \fII\fP has been found whose inode number for `.' does
810 does not equal \fII\fP.
811 .LP
812 Possible responses to the FIX prompt are:
813 .IP YES
814 change the inode number for `.' to be equal to \fII\fP.
815 .IP NO
816 leave the inode number for `.' unchanged.
817 .sp
818 .LP
819 .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
820 .br
821 A directory \fII\fP has been found whose first entry is unallocated.
822 .LP
823 Possible responses to the FIX prompt are:
824 .IP YES
825 build an entry for `.' with inode number equal to \fII\fP.
826 .IP NO
827 leave the directory unchanged.
828 .sp
829 .LP
830 .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
831 .br
832 .B "CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS \fIF\fP"
833 .br
834 A directory \fII\fP has been found whose first entry is \fIF\fP.
835 .I Fsck_ffs
836 cannot resolve this problem.
837 The file system should be mounted and the offending entry \fIF\fP
838 moved elsewhere.
839 The file system should then be unmounted and
840 .I fsck_ffs
841 should be run again.
842 .sp
843 .LP
844 .B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
845 .br
846 .B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `.'"
847 .br
848 A directory \fII\fP has been found whose first entry is not `.'.
849 .I Fsck_ffs
850 cannot resolve this problem as it should never happen.
851 See a guru.
852 .sp
853 .LP
854 .B "EXTRA `.' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
855 .br
856 A directory \fII\fP has been found that has more than one entry for `.'.
857 .LP
858 Possible responses to the FIX prompt are:
859 .IP YES
860 remove the extra entry for `.'.
861 .IP NO
862 leave the directory unchanged.
863 .sp
864 .LP
865 .B "BAD INODE NUMBER FOR `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
866 .br
867 A directory \fII\fP has been found whose inode number for `..' does
868 does not equal the parent of \fII\fP.
869 .LP
870 Possible responses to the FIX prompt are:
871 .IP YES
872 change the inode number for `..' to be equal to the parent of \fII\fP
873 (``\fB..\fP'' in the root inode points to itself).
874 .IP NO
875 leave the inode number for `..' unchanged.
876 .sp
877 .LP
878 .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
879 .br
880 A directory \fII\fP has been found whose second entry is unallocated.
881 .LP
882 Possible responses to the FIX prompt are:
883 .IP YES
884 build an entry for `..' with inode number equal to the parent of \fII\fP
885 (``\fB..\fP'' in the root inode points to itself).
886 .IP NO
887 leave the directory unchanged.
888 .sp
889 .LP
890 .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
891 .br
892 .B "CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS \fIF\fP"
893 .br
894 A directory \fII\fP has been found whose second entry is \fIF\fP.
895 .I Fsck_ffs
896 cannot resolve this problem.
897 The file system should be mounted and the offending entry \fIF\fP
898 moved elsewhere.
899 The file system should then be unmounted and
900 .I fsck_ffs
901 should be run again.
902 .sp
903 .LP
904 .B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
905 .br
906 .B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `..'"
907 .br
908 A directory \fII\fP has been found whose second entry is not `..'.
909 .I Fsck_ffs
910 cannot resolve this problem.
911 The file system should be mounted and the second entry in the directory
912 moved elsewhere.
913 The file system should then be unmounted and
914 .I fsck_ffs
915 should be run again.
916 .sp
917 .LP
918 .B "EXTRA `..' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
919 .br
920 A directory \fII\fP has been found that has more than one entry for `..'.
921 .LP
922 Possible responses to the FIX prompt are:
923 .IP YES
924 remove the extra entry for `..'.
925 .IP NO
926 leave the directory unchanged.
927 .sp
928 .LP
929 .B "\fIN\fP IS AN EXTRANEOUS HARD LINK TO A DIRECTORY \fID\fP (REMOVE)
930 .br
931 .I Fsck_ffs
932 has found a hard link, \fIN\fP, to a directory, \fID\fP.
933 When preen'ing the extraneous links are ignored.
934 .LP
935 Possible responses to the REMOVE prompt are:
936 .IP YES
937 delete the extraneous entry, \fIN\fP.
938 .IP NO
939 ignore the error condition.
940 .sp
941 .LP
942 .B "BAD INODE \fIS\fP TO DESCEND"
943 .br
944 An internal error has caused an impossible state \fIS\fP to be passed to the
945 routine that descends the file system directory structure.
946 .I Fsck_ffs
947 exits.
948 See a guru.
949 .sp
950 .LP
951 .B "BAD RETURN STATE \fIS\fP FROM DESCEND"
952 .br
953 An internal error has caused an impossible state \fIS\fP to be returned
954 from the routine that descends the file system directory structure.
955 .I Fsck_ffs
956 exits.
957 See a guru.
958 .sp
959 .LP
960 .B "BAD STATE \fIS\fP FOR ROOT INODE"
961 .br
962 An internal error has caused an impossible state \fIS\fP to be assigned
963 to the root inode.
964 .I Fsck_ffs
965 exits.
966 See a guru.
967 .NH 2
968 Phase 3 \- Check Connectivity
969 .PP
970 This phase concerns itself with the directory connectivity seen in
971 Phase 2.
972 This section lists error conditions resulting from
973 unreferenced directories,
974 and missing or full
975 .I lost+found
976 directories.
977 .sp
978 .LP
979 .B "UNREF DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
980 .br
981 The directory inode \fII\fP was not connected to a directory entry
982 when the file system was traversed.
983 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
984 modify time \fIT\fP of directory inode \fII\fP are printed.
985 When preen'ing, the directory is reconnected if its size is non-zero,
986 otherwise it is cleared.
987 .LP
988 Possible responses to the RECONNECT prompt are:
989 .IP YES
990 reconnect directory inode \fII\fP to the file system in the
991 directory for lost files (usually \fIlost+found\fP).
992 This may invoke the
993 .I lost+found
994 error condition in Phase 3
995 if there are problems connecting directory inode \fII\fP to \fIlost+found\fP.
996 This may also invoke the CONNECTED error condition in Phase 3 if the link
997 was successful.
998 .IP NO
999 ignore this error condition.
1000 This will always invoke the UNREF error condition in Phase 4.
1001 .sp
1002 .LP
1003 .B "NO lost+found DIRECTORY (CREATE)"
1004 .br
1005 There is no
1006 .I lost+found
1007 directory in the root directory of the file system;
1008 When preen'ing
1009 .I fsck_ffs
1010 tries to create a \fIlost+found\fP directory.
1011 .LP
1012 Possible responses to the CREATE prompt are:
1013 .IP YES
1014 create a \fIlost+found\fP directory in the root of the file system.
1015 This may raise the message:
1016 .br
1017 .B "NO SPACE LEFT IN / (EXPAND)"
1018 .br
1019 See below for the possible responses.
1020 Inability to create a \fIlost+found\fP directory generates the message:
1021 .br
1022 .B "SORRY. CANNOT CREATE lost+found DIRECTORY"
1023 .br
1024 and aborts the attempt to linkup the lost inode.
1025 This will always invoke the UNREF error condition in Phase 4.
1026 .IP NO
1027 abort the attempt to linkup the lost inode.
1028 This will always invoke the UNREF error condition in Phase 4.
1029 .sp
1030 .LP
1031 .B "lost+found IS NOT A DIRECTORY (REALLOCATE)"
1032 .br
1033 The entry for
1034 .I lost+found
1035 is not a directory.
1036 .LP
1037 Possible responses to the REALLOCATE prompt are:
1038 .IP YES
1039 allocate a directory inode, and change \fIlost+found\fP to reference it.
1040 The previous inode reference by the \fIlost+found\fP name is not cleared.
1041 Thus it will either be reclaimed as an UNREF'ed inode or have its
1042 link count ADJUST'ed later in this Phase.
1043 Inability to create a \fIlost+found\fP directory generates the message:
1044 .br
1045 .B "SORRY. CANNOT CREATE lost+found DIRECTORY"
1046 .br
1047 and aborts the attempt to linkup the lost inode.
1048 This will always invoke the UNREF error condition in Phase 4.
1049 .IP NO
1050 abort the attempt to linkup the lost inode.
1051 This will always invoke the UNREF error condition in Phase 4.
1052 .sp
1053 .LP
1054 .B "NO SPACE LEFT IN /lost+found (EXPAND)"
1055 .br
1056 There is no space to add another entry to the
1057 .I lost+found
1058 directory in the root directory
1059 of the file system.
1060 When preen'ing the
1061 .I lost+found
1062 directory is expanded.
1063 .LP
1064 Possible responses to the EXPAND prompt are:
1065 .IP YES
1066 the
1067 .I lost+found
1068 directory is expanded to make room for the new entry.
1069 If the attempted expansion fails
1070 .I fsck_ffs
1071 prints the message:
1072 .br
1073 .B "SORRY. NO SPACE IN lost+found DIRECTORY"
1074 .br
1075 and aborts the attempt to linkup the lost inode.
1076 This will always invoke the UNREF error condition in Phase 4.
1077 Clean out unnecessary entries in
1078 .I lost+found .
1079 This error is fatal if the file system is being preen'ed.
1080 .IP NO
1081 abort the attempt to linkup the lost inode.
1082 This will always invoke the UNREF error condition in Phase 4.
1083 .sp
1084 .LP
1085 .B "DIR I=\fII1\fP CONNECTED. PARENT WAS I=\fII2\fP"
1086 .br
1087 This is an advisory message indicating a directory inode \fII1\fP was
1088 successfully connected to the
1089 .I lost+found
1090 directory.
1091 The parent inode \fII2\fP of the directory inode \fII1\fP is
1092 replaced by the inode number of the
1093 .I lost+found
1094 directory.
1095 .sp
1096 .LP
1097 .B "DIRECTORY \fIF\fP LENGTH \fIS\fP NOT MULTIPLE OF \fIB\fP (ADJUST)
1098 .br
1099 A directory \fIF\fP has been found with size \fIS\fP that is not
1100 a multiple of the directory blocksize \fIB\fP
1101 (this can reoccur in Phase 3 if it is not adjusted in Phase 2).
1102 .LP
1103 Possible responses to the ADJUST prompt are:
1104 .IP YES
1105 the length is rounded up to the appropriate block size.
1106 This error can occur on 4.2BSD file systems.
1107 Thus when preen'ing the file system only a warning is printed
1108 and the directory is adjusted.
1109 .IP NO
1110 ignore the error condition.
1111 .sp
1112 .LP
1113 .B "BAD INODE \fIS\fP TO DESCEND"
1114 .br
1115 An internal error has caused an impossible state \fIS\fP to be passed to the
1116 routine that descends the file system directory structure.
1117 .I Fsck_ffs
1118 exits.
1119 See a guru.
1120 .NH 2
1121 Phase 4 \- Check Reference Counts
1122 .PP
1123 This phase concerns itself with the link count information
1124 seen in Phase 2 and Phase 3.
1125 This section lists error conditions resulting from
1126 unreferenced files,
1127 missing or full
1128 .I lost+found
1129 directory,
1130 incorrect link counts for files, directories, symbolic links, or special files,
1131 unreferenced files, symbolic links, and directories,
1132 and bad or duplicate blocks in files, symbolic links, and directories.
1133 All errors in this phase are correctable if the file system is being preen'ed
1134 except running out of space in the \fIlost+found\fP directory.
1135 .sp
1136 .LP
1137 .B "UNREF FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
1138 .br
1139 Inode \fII\fP was not connected to a directory entry
1140 when the file system was traversed.
1141 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
1142 modify time \fIT\fP of inode \fII\fP are printed.
1143 When preen'ing the file is cleared if either its size or its
1144 link count is zero,
1145 otherwise it is reconnected.
1146 .LP
1147 Possible responses to the RECONNECT prompt are:
1148 .IP YES
1149 reconnect inode \fII\fP to the file system in the directory for
1150 lost files (usually \fIlost+found\fP).
1151 This may invoke the
1152 .I lost+found
1153 error condition in Phase 4
1154 if there are problems connecting inode \fII\fP to
1155 .I lost+found .
1156 .IP NO
1157 ignore this error condition.
1158 This will always invoke the CLEAR error condition in Phase 4.
1159 .sp
1160 .LP
1161 .B "(CLEAR)"
1162 .br
1163 The inode mentioned in the immediately previous error condition can not be
1164 reconnected.
1165 This cannot occur if the file system is being preen'ed,
1166 since lack of space to reconnect files is a fatal error.
1167 .LP
1168 Possible responses to the CLEAR prompt are:
1169 .IP YES
1170 de-allocate the inode mentioned in the immediately previous error condition by zeroing its contents.
1171 .IP NO
1172 ignore this error condition.
1173 .sp
1174 .LP
1175 .B "NO lost+found DIRECTORY (CREATE)"
1176 .br
1177 There is no
1178 .I lost+found
1179 directory in the root directory of the file system;
1180 When preen'ing
1181 .I fsck_ffs
1182 tries to create a \fIlost+found\fP directory.
1183 .LP
1184 Possible responses to the CREATE prompt are:
1185 .IP YES
1186 create a \fIlost+found\fP directory in the root of the file system.
1187 This may raise the message:
1188 .br
1189 .B "NO SPACE LEFT IN / (EXPAND)"
1190 .br
1191 See below for the possible responses.
1192 Inability to create a \fIlost+found\fP directory generates the message:
1193 .br
1194 .B "SORRY. CANNOT CREATE lost+found DIRECTORY"
1195 .br
1196 and aborts the attempt to linkup the lost inode.
1197 This will always invoke the UNREF error condition in Phase 4.
1198 .IP NO
1199 abort the attempt to linkup the lost inode.
1200 This will always invoke the UNREF error condition in Phase 4.
1201 .sp
1202 .LP
1203 .B "lost+found IS NOT A DIRECTORY (REALLOCATE)"
1204 .br
1205 The entry for
1206 .I lost+found
1207 is not a directory.
1208 .LP
1209 Possible responses to the REALLOCATE prompt are:
1210 .IP YES
1211 allocate a directory inode, and change \fIlost+found\fP to reference it.
1212 The previous inode reference by the \fIlost+found\fP name is not cleared.
1213 Thus it will either be reclaimed as an UNREF'ed inode or have its
1214 link count ADJUST'ed later in this Phase.
1215 Inability to create a \fIlost+found\fP directory generates the message:
1216 .br
1217 .B "SORRY. CANNOT CREATE lost+found DIRECTORY"
1218 .br
1219 and aborts the attempt to linkup the lost inode.
1220 This will always invoke the UNREF error condition in Phase 4.
1221 .IP NO
1222 abort the attempt to linkup the lost inode.
1223 This will always invoke the UNREF error condition in Phase 4.
1224 .sp
1225 .LP
1226 .B "NO SPACE LEFT IN /lost+found (EXPAND)"
1227 .br
1228 There is no space to add another entry to the
1229 .I lost+found
1230 directory in the root directory
1231 of the file system.
1232 When preen'ing the
1233 .I lost+found
1234 directory is expanded.
1235 .LP
1236 Possible responses to the EXPAND prompt are:
1237 .IP YES
1238 the
1239 .I lost+found
1240 directory is expanded to make room for the new entry.
1241 If the attempted expansion fails
1242 .I fsck_ffs
1243 prints the message:
1244 .br
1245 .B "SORRY. NO SPACE IN lost+found DIRECTORY"
1246 .br
1247 and aborts the attempt to linkup the lost inode.
1248 This will always invoke the UNREF error condition in Phase 4.
1249 Clean out unnecessary entries in
1250 .I lost+found .
1251 This error is fatal if the file system is being preen'ed.
1252 .IP NO
1253 abort the attempt to linkup the lost inode.
1254 This will always invoke the UNREF error condition in Phase 4.
1255 .sp
1256 .LP
1257 .B "LINK COUNT \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP COUNT=\fIX\fP SHOULD BE \fIY\fP (ADJUST)"
1258 .br
1259 The link count for inode \fII\fP,
1260 is \fIX\fP but should be \fIY\fP.
1261 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP
1262 are printed.
1263 When preen'ing the link count is adjusted unless the number of references
1264 is increasing, a condition that should never occur unless precipitated
1265 by a hardware failure.
1266 When the number of references is increasing under preen mode,
1267 .I fsck_ffs
1268 exits with the message:
1269 .br
1270 .B "LINK COUNT INCREASING"
1271 .LP
1272 Possible responses to the ADJUST prompt are:
1273 .IP YES
1274 replace the link count of file inode \fII\fP with \fIY\fP.
1275 .IP NO
1276 ignore this error condition.
1277 .sp
1278 .LP
1279 .B "UNREF \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1280 .br
1281 Inode \fII\fP, was not connected to a directory entry when the
1282 file system was traversed.
1283 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1284 and modify time \fIT\fP of inode \fII\fP
1285 are printed.
1286 When preen'ing,
1287 this is a file that was not connected because its size or link count was zero,
1288 hence it is cleared.
1289 .LP
1290 Possible responses to the CLEAR prompt are:
1291 .IP YES
1292 de-allocate inode \fII\fP by zeroing its contents.
1293 .IP NO
1294 ignore this error condition.
1295 .sp
1296 .LP
1297 .B "BAD/DUP \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1298 .br
1299 Phase 1 or Phase 1b have found duplicate blocks
1300 or bad blocks associated with
1301 inode \fII\fP.
1302 The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1303 and modify time \fIT\fP of inode \fII\fP
1304 are printed.
1305 This error cannot arise when the file system is being preen'ed,
1306 as it would have caused a fatal error earlier.
1307 .LP
1308 Possible responses to the CLEAR prompt are:
1309 .IP YES
1310 de-allocate inode \fII\fP by zeroing its contents.
1311 .IP NO
1312 ignore this error condition.
1313 .NH 2
1314 Phase 5 - Check Cyl groups
1315 .PP
1316 This phase concerns itself with the free-block and used-inode maps.
1317 This section lists error conditions resulting from
1318 allocated blocks in the free-block maps,
1319 free blocks missing from free-block maps,
1320 and the total free-block count incorrect.
1321 It also lists error conditions resulting from
1322 free inodes in the used-inode maps,
1323 allocated inodes missing from used-inode maps,
1324 and the total used-inode count incorrect.
1325 .sp
1326 .LP
1327 .B "CG \fIC\fP: BAD MAGIC NUMBER"
1328 .br
1329 The magic number of cylinder group \fIC\fP is wrong.
1330 This usually indicates that the cylinder group maps have been destroyed.
1331 When running manually the cylinder group is marked as needing
1332 to be reconstructed.
1333 This error is fatal if the file system is being preen'ed.
1334 .sp
1335 .LP
1336 .B "BLK(S) MISSING IN BIT MAPS (SALVAGE)"
1337 .br
1338 A cylinder group block map is missing some free blocks.
1339 During preen'ing the maps are reconstructed.
1340 .LP
1341 Possible responses to the SALVAGE prompt are:
1342 .IP YES
1343 reconstruct the free block map.
1344 .IP NO
1345 ignore this error condition.
1346 .sp
1347 .LP
1348 .B "SUMMARY INFORMATION BAD (SALVAGE)"
1349 .br
1350 The summary information was found to be incorrect.
1351 When preen'ing,
1352 the summary information is recomputed.
1353 .LP
1354 Possible responses to the SALVAGE prompt are:
1355 .IP YES
1356 reconstruct the summary information.
1357 .IP NO
1358 ignore this error condition.
1359 .sp
1360 .LP
1361 .B "FREE BLK COUNT(S) WRONG IN SUPERBLOCK (SALVAGE)"
1362 .br
1363 The superblock free block information was found to be incorrect.
1364 When preen'ing,
1365 the superblock free block information is recomputed.
1366 .LP
1367 Possible responses to the SALVAGE prompt are:
1368 .IP YES
1369 reconstruct the superblock free block information.
1370 .IP NO
1371 ignore this error condition.
1372 .NH 2
1373 Cleanup
1374 .PP
1375 Once a file system has been checked, a few cleanup functions are performed.
1376 This section lists advisory messages about
1377 the file system
1378 and modify status of the file system.
1379 .sp
1380 .LP
1381 .B "\fIV\fP files, \fIW\fP used, \fIX\fP free (\fIY\fP frags, \fIZ\fP blocks)"
1382 .br
1383 This is an advisory message indicating that
1384 the file system checked contained
1385 \fIV\fP files using
1386 \fIW\fP fragment sized blocks leaving
1387 \fIX\fP fragment sized blocks free in the file system.
1388 The numbers in parenthesis breaks the free count down into
1389 \fIY\fP free fragments and
1390 \fIZ\fP free full sized blocks.
1391 .sp
1392 .LP
1393 .B "***** REBOOT UNIX *****"
1394 .br
1395 This is an advisory message indicating that
1396 the root file system has been modified by
1397 .I fsck_ffs.
1398 If UNIX is not rebooted immediately,
1399 the work done by
1400 .I fsck_ffs
1401 may be undone by the in-core copies of tables
1402 UNIX keeps.
1403 When preen'ing,
1404 .I fsck_ffs
1405 will exit with a code of 4.
1406 The standard auto-reboot script distributed with 4.3BSD
1407 interprets an exit code of 4 by issuing a reboot system call.
1408 .sp
1409 .LP
1410 .B "***** FILE SYSTEM WAS MODIFIED *****"
1411 .br
1412 This is an advisory message indicating that
1413 the current file system was modified by
1414 .I fsck_ffs.
1415 If this file system is mounted or is the current root file system,
1416 .I fsck_ffs
1417 should be halted and UNIX rebooted.
1418 If UNIX is not rebooted immediately,
1419 the work done by
1420 .I fsck_ffs
1421 may be undone by the in-core copies of tables
1422 UNIX keeps.