Deleted Added
sdiff udiff text old ( 96707 ) new ( 102231 )
full compact
4.t (96707) 4.t (102231)
1.\" Copyright (c) 1982, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 15 unchanged lines hidden (view full) ---

24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
1.\" Copyright (c) 1982, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 15 unchanged lines hidden (view full) ---

24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" $FreeBSD: head/sbin/fsck_ffs/SMM.doc/4.t 96707 2002-05-16 04:10:46Z trhodes $
32.\" $FreeBSD: head/sbin/fsck_ffs/SMM.doc/4.t 102231 2002-08-21 18:11:48Z trhodes $
33.\" @(#)4.t 8.1 (Berkeley) 6/5/93
34.\"
35.ds RH Appendix A \- Fsck_ffs Error Conditions
36.NH
37Appendix A \- Fsck_ffs Error Conditions
38.NH 2
39Conventions
40.PP
41.I Fsck_ffs
42is
33.\" @(#)4.t 8.1 (Berkeley) 6/5/93
34.\"
35.ds RH Appendix A \- Fsck_ffs Error Conditions
36.NH
37Appendix A \- Fsck_ffs Error Conditions
38.NH 2
39Conventions
40.PP
41.I Fsck_ffs
42is
43a multi-pass filesystem check program.
44Each filesystem pass invokes a different Phase of the
43a multi-pass file system check program.
44Each file system pass invokes a different Phase of the
45.I fsck_ffs
46program.
47After the initial setup,
48.I fsck_ffs
45.I fsck_ffs
46program.
47After the initial setup,
48.I fsck_ffs
49performs successive Phases over each filesystem,
49performs successive Phases over each file system,
50checking blocks and sizes,
51path-names,
52connectivity,
53reference counts,
54and the map of free blocks,
55(possibly rebuilding it),
56and performs some cleanup.
57.LP
58Normally
59.I fsck_ffs
60is run non-interactively to
61.I preen
50checking blocks and sizes,
51path-names,
52connectivity,
53reference counts,
54and the map of free blocks,
55(possibly rebuilding it),
56and performs some cleanup.
57.LP
58Normally
59.I fsck_ffs
60is run non-interactively to
61.I preen
62the filesystems after an unclean halt.
63While preen'ing a filesystem,
62the file systems after an unclean halt.
63While preen'ing a file system,
64it will only fix corruptions that are expected
65to occur from an unclean halt.
66These actions are a proper subset of the actions that
67.I fsck_ffs
68will take when it is running interactively.
69Throughout this appendix many errors have several options
70that the operator can take.
71When an inconsistency is detected,

--- 15 unchanged lines hidden (view full) ---

87.I fsck_ffs
88program in which they can occur.
89The error conditions that may occur
90in more than one Phase
91will be discussed in initialization.
92.NH 2
93Initialization
94.PP
64it will only fix corruptions that are expected
65to occur from an unclean halt.
66These actions are a proper subset of the actions that
67.I fsck_ffs
68will take when it is running interactively.
69Throughout this appendix many errors have several options
70that the operator can take.
71When an inconsistency is detected,

--- 15 unchanged lines hidden (view full) ---

87.I fsck_ffs
88program in which they can occur.
89The error conditions that may occur
90in more than one Phase
91will be discussed in initialization.
92.NH 2
93Initialization
94.PP
95Before a filesystem check can be performed, certain
95Before a file system check can be performed, certain
96tables have to be set up and certain files opened.
97This section concerns itself with the opening of files and
98the initialization of tables.
99This section lists error conditions resulting from
100command line options,
101memory requests,
102opening of files,
103status of files,
96tables have to be set up and certain files opened.
97This section concerns itself with the opening of files and
98the initialization of tables.
99This section lists error conditions resulting from
100command line options,
101memory requests,
102opening of files,
103status of files,
104filesystem size checks,
104file system size checks,
105and creation of the scratch file.
106All the initialization errors are fatal
105and creation of the scratch file.
106All the initialization errors are fatal
107when the filesystem is being preen'ed.
107when the file system is being preen'ed.
108.sp
109.LP
110.B "\fIC\fP option?"
111.br
112\fIC\fP is not a legal option to
113.I fsck_ffs ;
114legal options are \-b, \-c, \-y, \-n, and \-p.
115.I Fsck_ffs

--- 17 unchanged lines hidden (view full) ---

133This should never happen.
134.I Fsck_ffs
135terminates on this error condition.
136See a guru.
137.sp
138.LP
139.B "Can't open checklist file: \fIF\fP"
140.br
108.sp
109.LP
110.B "\fIC\fP option?"
111.br
112\fIC\fP is not a legal option to
113.I fsck_ffs ;
114legal options are \-b, \-c, \-y, \-n, and \-p.
115.I Fsck_ffs

--- 17 unchanged lines hidden (view full) ---

133This should never happen.
134.I Fsck_ffs
135terminates on this error condition.
136See a guru.
137.sp
138.LP
139.B "Can't open checklist file: \fIF\fP"
140.br
141The filesystem checklist file
141The file system checklist file
142\fIF\fP (usually
143.I /etc/fstab )
144can not be opened for reading.
145.I Fsck_ffs
146terminates on this error condition.
147Check access modes of \fIF\fP.
148.sp
149.LP

--- 7 unchanged lines hidden (view full) ---

157See a guru.
158.sp
159.LP
160.B "Can't stat \fIF\fP"
161.br
162.B "Can't make sense out of name \fIF\fP"
163.br
164.I Fsck_ffs 's
142\fIF\fP (usually
143.I /etc/fstab )
144can not be opened for reading.
145.I Fsck_ffs
146terminates on this error condition.
147Check access modes of \fIF\fP.
148.sp
149.LP

--- 7 unchanged lines hidden (view full) ---

157See a guru.
158.sp
159.LP
160.B "Can't stat \fIF\fP"
161.br
162.B "Can't make sense out of name \fIF\fP"
163.br
164.I Fsck_ffs 's
165request for statistics about the filesystem \fIF\fP failed.
165request for statistics about the file system \fIF\fP failed.
166When running manually,
166When running manually,
167it ignores this filesystem
168and continues checking the next filesystem given.
167it ignores this file system
168and continues checking the next file system given.
169Check access modes of \fIF\fP.
170.sp
171.LP
172.B "Can't open \fIF\fP"
173.br
174.I Fsck_ffs 's
169Check access modes of \fIF\fP.
170.sp
171.LP
172.B "Can't open \fIF\fP"
173.br
174.I Fsck_ffs 's
175request attempt to open the filesystem \fIF\fP failed.
176When running manually, it ignores this filesystem
177and continues checking the next filesystem given.
175request attempt to open the file system \fIF\fP failed.
176When running manually, it ignores this file system
177and continues checking the next file system given.
178Check access modes of \fIF\fP.
179.sp
180.LP
181.B "\fIF\fP: (NO WRITE)"
182.br
183Either the \-n flag was specified or
184.I fsck_ffs 's
178Check access modes of \fIF\fP.
179.sp
180.LP
181.B "\fIF\fP: (NO WRITE)"
182.br
183Either the \-n flag was specified or
184.I fsck_ffs 's
185attempt to open the filesystem \fIF\fP for writing failed.
185attempt to open the file system \fIF\fP for writing failed.
186When running manually,
187all the diagnostics are printed out,
188but no modifications are attempted to fix them.
189.sp
190.LP
191.B "file is not a block or character device; OK"
192.br
193You have given
194.I fsck_ffs
195a regular file name by mistake.
196Check the type of the file specified.
197.LP
198Possible responses to the OK prompt are:
199.IP YES
200ignore this error condition.
201.IP NO
186When running manually,
187all the diagnostics are printed out,
188but no modifications are attempted to fix them.
189.sp
190.LP
191.B "file is not a block or character device; OK"
192.br
193You have given
194.I fsck_ffs
195a regular file name by mistake.
196Check the type of the file specified.
197.LP
198Possible responses to the OK prompt are:
199.IP YES
200ignore this error condition.
201.IP NO
202ignore this filesystem and continues checking
203the next filesystem given.
202ignore this file system and continues checking
203the next file system given.
204.sp
205.LP
206.B "UNDEFINED OPTIMIZATION IN SUPERBLOCK (SET TO DEFAULT)"
207.br
208The superblock optimization parameter is neither OPT_TIME
209nor OPT_SPACE.
210.LP
211Possible responses to the SET TO DEFAULT prompt are:

--- 17 unchanged lines hidden (view full) ---

229(If some other percentage is desired,
230it can be set using \fItunefs\fP(8).)
231.IP NO
232ignore this error condition.
233.sp
234.LP
235.B "IMPOSSIBLE INTERLEAVE=\fID\fP IN SUPERBLOCK (SET TO DEFAULT)"
236.br
204.sp
205.LP
206.B "UNDEFINED OPTIMIZATION IN SUPERBLOCK (SET TO DEFAULT)"
207.br
208The superblock optimization parameter is neither OPT_TIME
209nor OPT_SPACE.
210.LP
211Possible responses to the SET TO DEFAULT prompt are:

--- 17 unchanged lines hidden (view full) ---

229(If some other percentage is desired,
230it can be set using \fItunefs\fP(8).)
231.IP NO
232ignore this error condition.
233.sp
234.LP
235.B "IMPOSSIBLE INTERLEAVE=\fID\fP IN SUPERBLOCK (SET TO DEFAULT)"
236.br
237The filesystem interleave is less than or equal to zero.
237The file system interleave is less than or equal to zero.
238.LP
239Possible responses to the SET TO DEFAULT prompt are:
240.IP YES
241The interleave parameter is set to 1.
242.IP NO
243ignore this error condition.
244.sp
245.LP

--- 30 unchanged lines hidden (view full) ---

276.B "USE -b OPTION TO FSCK_FFS TO SPECIFY LOCATION OF AN ALTERNATE"
277.br
278.B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck_ffs(8)."
279.br
280The super block has been corrupted.
281An alternative super block must be selected from among those
282listed by
283.I newfs
238.LP
239Possible responses to the SET TO DEFAULT prompt are:
240.IP YES
241The interleave parameter is set to 1.
242.IP NO
243ignore this error condition.
244.sp
245.LP

--- 30 unchanged lines hidden (view full) ---

276.B "USE -b OPTION TO FSCK_FFS TO SPECIFY LOCATION OF AN ALTERNATE"
277.br
278.B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck_ffs(8)."
279.br
280The super block has been corrupted.
281An alternative super block must be selected from among those
282listed by
283.I newfs
284(8) when the filesystem was created.
285For filesystems with a blocksize less than 32K,
284(8) when the file system was created.
285For file systems with a blocksize less than 32K,
286specifying \-b 32 is a good first choice.
287.sp
288.LP
289.B "INTERNAL INCONSISTENCY: \fIM\fP"
290.br
291.I Fsck_ffs 's
292has had an internal panic, whose message is specified as \fIM\fP.
293This should never happen.
294See a guru.
295.sp
296.LP
297.B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)"
298.br
299.I Fsck_ffs 's
300request for moving to a specified block number \fIB\fP in
286specifying \-b 32 is a good first choice.
287.sp
288.LP
289.B "INTERNAL INCONSISTENCY: \fIM\fP"
290.br
291.I Fsck_ffs 's
292has had an internal panic, whose message is specified as \fIM\fP.
293This should never happen.
294See a guru.
295.sp
296.LP
297.B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)"
298.br
299.I Fsck_ffs 's
300request for moving to a specified block number \fIB\fP in
301the filesystem failed.
301the file system failed.
302This should never happen.
303See a guru.
304.LP
305Possible responses to the CONTINUE prompt are:
306.IP YES
302This should never happen.
303See a guru.
304.LP
305Possible responses to the CONTINUE prompt are:
306.IP YES
307attempt to continue to run the filesystem check.
307attempt to continue to run the file system check.
308Often,
309however the problem will persist.
308Often,
309however the problem will persist.
310This error condition will not allow a complete check of the filesystem.
310This error condition will not allow a complete check of the file system.
311A second run of
312.I fsck_ffs
311A second run of
312.I fsck_ffs
313should be made to re-check this filesystem.
313should be made to re-check this file system.
314If the block was part of the virtual memory buffer
315cache,
316.I fsck_ffs
317will terminate with the message ``Fatal I/O error''.
318.IP NO
319terminate the program.
320.sp
321.LP
322.B "CAN NOT READ: BLK \fIB\fP (CONTINUE)"
323.br
324.I Fsck_ffs 's
325request for reading a specified block number \fIB\fP in
314If the block was part of the virtual memory buffer
315cache,
316.I fsck_ffs
317will terminate with the message ``Fatal I/O error''.
318.IP NO
319terminate the program.
320.sp
321.LP
322.B "CAN NOT READ: BLK \fIB\fP (CONTINUE)"
323.br
324.I Fsck_ffs 's
325request for reading a specified block number \fIB\fP in
326the filesystem failed.
326the file system failed.
327This should never happen.
328See a guru.
329.LP
330Possible responses to the CONTINUE prompt are:
331.IP YES
327This should never happen.
328See a guru.
329.LP
330Possible responses to the CONTINUE prompt are:
331.IP YES
332attempt to continue to run the filesystem check.
332attempt to continue to run the file system check.
333It will retry the read and print out the message:
334.br
335.B "THE FOLLOWING SECTORS COULD NOT BE READ: \fIN\fP"
336.br
337where \fIN\fP indicates the sectors that could not be read.
338If
339.I fsck_ffs
340ever tries to write back one of the blocks on which the read failed
341it will print the message:
342.br
343.B "WRITING ZERO'ED BLOCK \fIN\fP TO DISK"
344.br
345where \fIN\fP indicates the sector that was written with zero's.
346If the disk is experiencing hardware problems, the problem will persist.
333It will retry the read and print out the message:
334.br
335.B "THE FOLLOWING SECTORS COULD NOT BE READ: \fIN\fP"
336.br
337where \fIN\fP indicates the sectors that could not be read.
338If
339.I fsck_ffs
340ever tries to write back one of the blocks on which the read failed
341it will print the message:
342.br
343.B "WRITING ZERO'ED BLOCK \fIN\fP TO DISK"
344.br
345where \fIN\fP indicates the sector that was written with zero's.
346If the disk is experiencing hardware problems, the problem will persist.
347This error condition will not allow a complete check of the filesystem.
347This error condition will not allow a complete check of the file system.
348A second run of
349.I fsck_ffs
348A second run of
349.I fsck_ffs
350should be made to re-check this filesystem.
350should be made to re-check this file system.
351If the block was part of the virtual memory buffer
352cache,
353.I fsck_ffs
354will terminate with the message ``Fatal I/O error''.
355.IP NO
356terminate the program.
357.sp
358.LP
359.B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)"
360.br
361.I Fsck_ffs 's
362request for writing a specified block number \fIB\fP
351If the block was part of the virtual memory buffer
352cache,
353.I fsck_ffs
354will terminate with the message ``Fatal I/O error''.
355.IP NO
356terminate the program.
357.sp
358.LP
359.B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)"
360.br
361.I Fsck_ffs 's
362request for writing a specified block number \fIB\fP
363in the filesystem failed.
363in the file system failed.
364The disk is write-protected;
365check the write protect lock on the drive.
366If that is not the problem, see a guru.
367.LP
368Possible responses to the CONTINUE prompt are:
369.IP YES
364The disk is write-protected;
365check the write protect lock on the drive.
366If that is not the problem, see a guru.
367.LP
368Possible responses to the CONTINUE prompt are:
369.IP YES
370attempt to continue to run the filesystem check.
370attempt to continue to run the file system check.
371The write operation will be retried with the failed blocks
372indicated by the message:
373.br
374.B "THE FOLLOWING SECTORS COULD NOT BE WRITTEN: \fIN\fP"
375.br
376where \fIN\fP indicates the sectors that could not be written.
377If the disk is experiencing hardware problems, the problem will persist.
371The write operation will be retried with the failed blocks
372indicated by the message:
373.br
374.B "THE FOLLOWING SECTORS COULD NOT BE WRITTEN: \fIN\fP"
375.br
376where \fIN\fP indicates the sectors that could not be written.
377If the disk is experiencing hardware problems, the problem will persist.
378This error condition will not allow a complete check of the filesystem.
378This error condition will not allow a complete check of the file system.
379A second run of
380.I fsck_ffs
379A second run of
380.I fsck_ffs
381should be made to re-check this filesystem.
381should be made to re-check this file system.
382If the block was part of the virtual memory buffer
383cache,
384.I fsck_ffs
385will terminate with the message ``Fatal I/O error''.
386.IP NO
387terminate the program.
388.sp
389.LP

--- 14 unchanged lines hidden (view full) ---

404setting up the zero-link-count table,
405examining inode block numbers for bad or duplicate blocks,
406checking inode size,
407and checking inode format.
408All errors in this phase except
409.B "INCORRECT BLOCK COUNT"
410and
411.B "PARTIALLY TRUNCATED INODE"
382If the block was part of the virtual memory buffer
383cache,
384.I fsck_ffs
385will terminate with the message ``Fatal I/O error''.
386.IP NO
387terminate the program.
388.sp
389.LP

--- 14 unchanged lines hidden (view full) ---

404setting up the zero-link-count table,
405examining inode block numbers for bad or duplicate blocks,
406checking inode size,
407and checking inode format.
408All errors in this phase except
409.B "INCORRECT BLOCK COUNT"
410and
411.B "PARTIALLY TRUNCATED INODE"
412are fatal if the filesystem is being preen'ed.
412are fatal if the file system is being preen'ed.
413.sp
414.LP
415.B "UNKNOWN FILE TYPE I=\fII\fP (CLEAR)"
416.br
417The mode word of the inode \fII\fP indicates that the inode is not a
418special block inode, special character inode, socket inode, regular inode,
419symbolic link, or directory inode.
420.LP

--- 8 unchanged lines hidden (view full) ---

429.LP
430.B "PARTIALLY TRUNCATED INODE I=\fII\fP (SALVAGE)"
431.br
432.I Fsck_ffs
433has found inode \fII\fP whose size is shorter than the number of
434blocks allocated to it.
435This condition should only occur if the system crashes while in the
436midst of truncating a file.
413.sp
414.LP
415.B "UNKNOWN FILE TYPE I=\fII\fP (CLEAR)"
416.br
417The mode word of the inode \fII\fP indicates that the inode is not a
418special block inode, special character inode, socket inode, regular inode,
419symbolic link, or directory inode.
420.LP

--- 8 unchanged lines hidden (view full) ---

429.LP
430.B "PARTIALLY TRUNCATED INODE I=\fII\fP (SALVAGE)"
431.br
432.I Fsck_ffs
433has found inode \fII\fP whose size is shorter than the number of
434blocks allocated to it.
435This condition should only occur if the system crashes while in the
436midst of truncating a file.
437When preen'ing the filesystem,
437When preen'ing the file system,
438.I fsck_ffs
439completes the truncation to the specified size.
440.LP
441Possible responses to SALVAGE are:
442.IP YES
443complete the truncation to the size specified in the inode.
444.IP NO
445ignore this error condition.

--- 6 unchanged lines hidden (view full) ---

452containing allocated inodes with a link count of
453zero cannot allocate more memory.
454Increase the virtual memory for
455.I fsck_ffs .
456.LP
457Possible responses to the CONTINUE prompt are:
458.IP YES
459continue with the program.
438.I fsck_ffs
439completes the truncation to the specified size.
440.LP
441Possible responses to SALVAGE are:
442.IP YES
443complete the truncation to the size specified in the inode.
444.IP NO
445ignore this error condition.

--- 6 unchanged lines hidden (view full) ---

452containing allocated inodes with a link count of
453zero cannot allocate more memory.
454Increase the virtual memory for
455.I fsck_ffs .
456.LP
457Possible responses to the CONTINUE prompt are:
458.IP YES
459continue with the program.
460This error condition will not allow a complete check of the filesystem.
460This error condition will not allow a complete check of the file system.
461A second run of
462.I fsck_ffs
461A second run of
462.I fsck_ffs
463should be made to re-check this filesystem.
463should be made to re-check this file system.
464If another allocated inode with a zero link count is found,
465this error condition is repeated.
466.IP NO
467terminate the program.
468.sp
469.LP
470.B "\fIB\fP BAD I=\fII\fP"
471.br
472Inode \fII\fP contains block number \fIB\fP with a number
464If another allocated inode with a zero link count is found,
465this error condition is repeated.
466.IP NO
467terminate the program.
468.sp
469.LP
470.B "\fIB\fP BAD I=\fII\fP"
471.br
472Inode \fII\fP contains block number \fIB\fP with a number
473lower than the number of the first data block in the filesystem or
473lower than the number of the first data block in the file system or
474greater than the number of the last block
474greater than the number of the last block
475in the filesystem.
475in the file system.
476This error condition may invoke the
477.B "EXCESSIVE BAD BLKS"
478error condition in Phase 1 (see next paragraph) if
476This error condition may invoke the
477.B "EXCESSIVE BAD BLKS"
478error condition in Phase 1 (see next paragraph) if
479inode \fII\fP has too many block numbers outside the filesystem range.
479inode \fII\fP has too many block numbers outside the file system range.
480This error condition will always invoke the
481.B "BAD/DUP"
482error condition in Phase 2 and Phase 4.
483.sp
484.LP
485.B "EXCESSIVE BAD BLKS I=\fII\fP (CONTINUE)"
486.br
487There is more than a tolerable number (usually 10) of blocks with a number
480This error condition will always invoke the
481.B "BAD/DUP"
482error condition in Phase 2 and Phase 4.
483.sp
484.LP
485.B "EXCESSIVE BAD BLKS I=\fII\fP (CONTINUE)"
486.br
487There is more than a tolerable number (usually 10) of blocks with a number
488lower than the number of the first data block in the filesystem or greater than
489the number of last block in the filesystem associated with inode \fII\fP.
488lower than the number of the first data block in the file system or greater than
489the number of last block in the file system associated with inode \fII\fP.
490.LP
491Possible responses to the CONTINUE prompt are:
492.IP YES
493ignore the rest of the blocks in this inode
490.LP
491Possible responses to the CONTINUE prompt are:
492.IP YES
493ignore the rest of the blocks in this inode
494and continue checking with the next inode in the filesystem.
495This error condition will not allow a complete check of the filesystem.
494and continue checking with the next inode in the file system.
495This error condition will not allow a complete check of the file system.
496A second run of
497.I fsck_ffs
496A second run of
497.I fsck_ffs
498should be made to re-check this filesystem.
498should be made to re-check this file system.
499.IP NO
500terminate the program.
501.sp
502.LP
503.B "BAD STATE DDD TO BLKERR"
504.br
505An internal error has scrambled
506.I fsck_ffs 's

--- 19 unchanged lines hidden (view full) ---

526.B "EXCESSIVE DUP BLKS I=\fII\fP (CONTINUE)"
527.br
528There is more than a tolerable number (usually 10) of blocks claimed by other
529inodes.
530.LP
531Possible responses to the CONTINUE prompt are:
532.IP YES
533ignore the rest of the blocks in this inode
499.IP NO
500terminate the program.
501.sp
502.LP
503.B "BAD STATE DDD TO BLKERR"
504.br
505An internal error has scrambled
506.I fsck_ffs 's

--- 19 unchanged lines hidden (view full) ---

526.B "EXCESSIVE DUP BLKS I=\fII\fP (CONTINUE)"
527.br
528There is more than a tolerable number (usually 10) of blocks claimed by other
529inodes.
530.LP
531Possible responses to the CONTINUE prompt are:
532.IP YES
533ignore the rest of the blocks in this inode
534and continue checking with the next inode in the filesystem.
535This error condition will not allow a complete check of the filesystem.
534and continue checking with the next inode in the file system.
535This error condition will not allow a complete check of the file system.
536A second run of
537.I fsck_ffs
536A second run of
537.I fsck_ffs
538should be made to re-check this filesystem.
538should be made to re-check this file system.
539.IP NO
540terminate the program.
541.sp
542.LP
543.B "DUP TABLE OVERFLOW (CONTINUE)"
544.br
545An internal table in
546.I fsck_ffs
547containing duplicate block numbers cannot allocate any more space.
548Increase the amount of virtual memory available to
549.I fsck_ffs .
550.LP
551Possible responses to the CONTINUE prompt are:
552.IP YES
553continue with the program.
539.IP NO
540terminate the program.
541.sp
542.LP
543.B "DUP TABLE OVERFLOW (CONTINUE)"
544.br
545An internal table in
546.I fsck_ffs
547containing duplicate block numbers cannot allocate any more space.
548Increase the amount of virtual memory available to
549.I fsck_ffs .
550.LP
551Possible responses to the CONTINUE prompt are:
552.IP YES
553continue with the program.
554This error condition will not allow a complete check of the filesystem.
554This error condition will not allow a complete check of the file system.
555A second run of
556.I fsck_ffs
555A second run of
556.I fsck_ffs
557should be made to re-check this filesystem.
557should be made to re-check this file system.
558If another duplicate block is found, this error condition will repeat.
559.IP NO
560terminate the program.
561.sp
562.LP
563.B "PARTIALLY ALLOCATED INODE I=\fII\fP (CLEAR)"
564.br
565Inode \fII\fP is neither allocated nor unallocated.

--- 14 unchanged lines hidden (view full) ---

580Possible responses to the CORRECT prompt are:
581.IP YES
582replace the block count of inode \fII\fP with \fIY\fP.
583.IP NO
584ignore this error condition.
585.NH 2
586Phase 1B: Rescan for More Dups
587.PP
558If another duplicate block is found, this error condition will repeat.
559.IP NO
560terminate the program.
561.sp
562.LP
563.B "PARTIALLY ALLOCATED INODE I=\fII\fP (CLEAR)"
564.br
565Inode \fII\fP is neither allocated nor unallocated.

--- 14 unchanged lines hidden (view full) ---

580Possible responses to the CORRECT prompt are:
581.IP YES
582replace the block count of inode \fII\fP with \fIY\fP.
583.IP NO
584ignore this error condition.
585.NH 2
586Phase 1B: Rescan for More Dups
587.PP
588When a duplicate block is found in the filesystem, the filesystem is
588When a duplicate block is found in the file system, the file system is
589rescanned to find the inode that previously claimed that block.
590This section lists the error condition when the duplicate block is found.
591.sp
592.LP
593.B "\fIB\fP DUP I=\fII\fP"
594.br
595Inode \fII\fP contains block number \fIB\fP that
596is already claimed by another inode.

--- 9 unchanged lines hidden (view full) ---

606pointing to
607error conditioned inodes
608from Phase 1 and Phase 1b.
609This section lists error conditions resulting from
610root inode mode and status,
611directory inode pointers in range,
612and directory entries pointing to bad inodes,
613and directory integrity checks.
589rescanned to find the inode that previously claimed that block.
590This section lists the error condition when the duplicate block is found.
591.sp
592.LP
593.B "\fIB\fP DUP I=\fII\fP"
594.br
595Inode \fII\fP contains block number \fIB\fP that
596is already claimed by another inode.

--- 9 unchanged lines hidden (view full) ---

606pointing to
607error conditioned inodes
608from Phase 1 and Phase 1b.
609This section lists error conditions resulting from
610root inode mode and status,
611directory inode pointers in range,
612and directory entries pointing to bad inodes,
613and directory integrity checks.
614All errors in this phase are fatal if the filesystem is being preen'ed,
614All errors in this phase are fatal if the file system is being preen'ed,
615except for directories not being a multiple of the blocks size
616and extraneous hard links.
617.sp
618.LP
619.B "ROOT INODE UNALLOCATED (ALLOCATE)"
620.br
621The root inode (usually inode number 2) has no allocate mode bits.
622This should never happen.

--- 43 unchanged lines hidden (view full) ---

666many error conditions will be produced.
667.IP NO
668terminate the program.
669.sp
670.LP
671.B "DUPS/BAD IN ROOT INODE (REALLOCATE)"
672.br
673Phase 1 or Phase 1b have found duplicate blocks
615except for directories not being a multiple of the blocks size
616and extraneous hard links.
617.sp
618.LP
619.B "ROOT INODE UNALLOCATED (ALLOCATE)"
620.br
621The root inode (usually inode number 2) has no allocate mode bits.
622This should never happen.

--- 43 unchanged lines hidden (view full) ---

666many error conditions will be produced.
667.IP NO
668terminate the program.
669.sp
670.LP
671.B "DUPS/BAD IN ROOT INODE (REALLOCATE)"
672.br
673Phase 1 or Phase 1b have found duplicate blocks
674or bad blocks in the root inode (usually inode number 2) for the filesystem.
674or bad blocks in the root inode (usually inode number 2) for the file system.
675.LP
676Possible responses to the REALLOCATE prompt are:
677.IP YES
678clear the existing contents of the root inode
679and reallocate it.
680The files and directories usually found in the root will be recovered
681in Phase 3 and put into
682.I lost+found .

--- 7 unchanged lines hidden (view full) ---

690will then prompt with
691.B "CONTINUE" .
692.LP
693Possible responses to the CONTINUE prompt are:
694.IP YES
695ignore the
696.B "DUPS/BAD"
697error condition in the root inode and
675.LP
676Possible responses to the REALLOCATE prompt are:
677.IP YES
678clear the existing contents of the root inode
679and reallocate it.
680The files and directories usually found in the root will be recovered
681in Phase 3 and put into
682.I lost+found .

--- 7 unchanged lines hidden (view full) ---

690will then prompt with
691.B "CONTINUE" .
692.LP
693Possible responses to the CONTINUE prompt are:
694.IP YES
695ignore the
696.B "DUPS/BAD"
697error condition in the root inode and
698attempt to continue to run the filesystem check.
698attempt to continue to run the file system check.
699If the root inode is not correct,
700then this may result in many other error conditions.
701.IP NO
702terminate the program.
703.sp
704.LP
705.B "NAME TOO LONG \fIF\fP"
706.br
707An excessively long path name has been found.
699If the root inode is not correct,
700then this may result in many other error conditions.
701.IP NO
702terminate the program.
703.sp
704.LP
705.B "NAME TOO LONG \fIF\fP"
706.br
707An excessively long path name has been found.
708This usually indicates loops in the filesystem name space.
708This usually indicates loops in the file system name space.
709This can occur if the super user has made circular links to directories.
710The offending links must be removed (by a guru).
711.sp
712.LP
713.B "I OUT OF RANGE I=\fII\fP NAME=\fIF\fP (REMOVE)"
714.br
715A directory entry \fIF\fP has an inode number \fII\fP that is greater than
716the end of the inode list.

--- 63 unchanged lines hidden (view full) ---

780.B "DIRECTORY \fIF\fP LENGTH \fIS\fP NOT MULTIPLE OF \fIB\fP (ADJUST)
781.br
782A directory \fIF\fP has been found with size \fIS\fP that is not
783a multiple of the directory blocksize \fIB\fP.
784.LP
785Possible responses to the ADJUST prompt are:
786.IP YES
787the length is rounded up to the appropriate block size.
709This can occur if the super user has made circular links to directories.
710The offending links must be removed (by a guru).
711.sp
712.LP
713.B "I OUT OF RANGE I=\fII\fP NAME=\fIF\fP (REMOVE)"
714.br
715A directory entry \fIF\fP has an inode number \fII\fP that is greater than
716the end of the inode list.

--- 63 unchanged lines hidden (view full) ---

780.B "DIRECTORY \fIF\fP LENGTH \fIS\fP NOT MULTIPLE OF \fIB\fP (ADJUST)
781.br
782A directory \fIF\fP has been found with size \fIS\fP that is not
783a multiple of the directory blocksize \fIB\fP.
784.LP
785Possible responses to the ADJUST prompt are:
786.IP YES
787the length is rounded up to the appropriate block size.
788This error can occur on 4.2BSD filesystems.
789Thus when preen'ing the filesystem only a warning is printed
788This error can occur on 4.2BSD file systems.
789Thus when preen'ing the file system only a warning is printed
790and the directory is adjusted.
791.IP NO
792ignore the error condition.
793.sp
794.LP
795.B "DIRECTORY CORRUPTED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (SALVAGE)"
796.br
797A directory with an inconsistent internal state has been found.

--- 34 unchanged lines hidden (view full) ---

832.LP
833.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
834.br
835.B "CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS \fIF\fP"
836.br
837A directory \fII\fP has been found whose first entry is \fIF\fP.
838.I Fsck_ffs
839cannot resolve this problem.
790and the directory is adjusted.
791.IP NO
792ignore the error condition.
793.sp
794.LP
795.B "DIRECTORY CORRUPTED I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (SALVAGE)"
796.br
797A directory with an inconsistent internal state has been found.

--- 34 unchanged lines hidden (view full) ---

832.LP
833.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
834.br
835.B "CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS \fIF\fP"
836.br
837A directory \fII\fP has been found whose first entry is \fIF\fP.
838.I Fsck_ffs
839cannot resolve this problem.
840The filesystem should be mounted and the offending entry \fIF\fP
840The file system should be mounted and the offending entry \fIF\fP
841moved elsewhere.
841moved elsewhere.
842The filesystem should then be unmounted and
842The file system should then be unmounted and
843.I fsck_ffs
844should be run again.
845.sp
846.LP
847.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
848.br
849.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `.'"
850.br

--- 41 unchanged lines hidden (view full) ---

892.LP
893.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
894.br
895.B "CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS \fIF\fP"
896.br
897A directory \fII\fP has been found whose second entry is \fIF\fP.
898.I Fsck_ffs
899cannot resolve this problem.
843.I fsck_ffs
844should be run again.
845.sp
846.LP
847.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
848.br
849.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `.'"
850.br

--- 41 unchanged lines hidden (view full) ---

892.LP
893.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
894.br
895.B "CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS \fIF\fP"
896.br
897A directory \fII\fP has been found whose second entry is \fIF\fP.
898.I Fsck_ffs
899cannot resolve this problem.
900The filesystem should be mounted and the offending entry \fIF\fP
900The file system should be mounted and the offending entry \fIF\fP
901moved elsewhere.
901moved elsewhere.
902The filesystem should then be unmounted and
902The file system should then be unmounted and
903.I fsck_ffs
904should be run again.
905.sp
906.LP
907.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
908.br
909.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `..'"
910.br
911A directory \fII\fP has been found whose second entry is not `..'.
912.I Fsck_ffs
913cannot resolve this problem.
903.I fsck_ffs
904should be run again.
905.sp
906.LP
907.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP"
908.br
909.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `..'"
910.br
911A directory \fII\fP has been found whose second entry is not `..'.
912.I Fsck_ffs
913cannot resolve this problem.
914The filesystem should be mounted and the second entry in the directory
914The file system should be mounted and the second entry in the directory
915moved elsewhere.
915moved elsewhere.
916The filesystem should then be unmounted and
916The file system should then be unmounted and
917.I fsck_ffs
918should be run again.
919.sp
920.LP
921.B "EXTRA `..' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
922.br
923A directory \fII\fP has been found that has more than one entry for `..'.
924.LP

--- 15 unchanged lines hidden (view full) ---

940delete the extraneous entry, \fIN\fP.
941.IP NO
942ignore the error condition.
943.sp
944.LP
945.B "BAD INODE \fIS\fP TO DESCEND"
946.br
947An internal error has caused an impossible state \fIS\fP to be passed to the
917.I fsck_ffs
918should be run again.
919.sp
920.LP
921.B "EXTRA `..' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)"
922.br
923A directory \fII\fP has been found that has more than one entry for `..'.
924.LP

--- 15 unchanged lines hidden (view full) ---

940delete the extraneous entry, \fIN\fP.
941.IP NO
942ignore the error condition.
943.sp
944.LP
945.B "BAD INODE \fIS\fP TO DESCEND"
946.br
947An internal error has caused an impossible state \fIS\fP to be passed to the
948routine that descends the filesystem directory structure.
948routine that descends the file system directory structure.
949.I Fsck_ffs
950exits.
951See a guru.
952.sp
953.LP
954.B "BAD RETURN STATE \fIS\fP FROM DESCEND"
955.br
956An internal error has caused an impossible state \fIS\fP to be returned
949.I Fsck_ffs
950exits.
951See a guru.
952.sp
953.LP
954.B "BAD RETURN STATE \fIS\fP FROM DESCEND"
955.br
956An internal error has caused an impossible state \fIS\fP to be returned
957from the routine that descends the filesystem directory structure.
957from the routine that descends the file system directory structure.
958.I Fsck_ffs
959exits.
960See a guru.
961.sp
962.LP
963.B "BAD STATE \fIS\fP FOR ROOT INODE"
964.br
965An internal error has caused an impossible state \fIS\fP to be assigned

--- 11 unchanged lines hidden (view full) ---

977and missing or full
978.I lost+found
979directories.
980.sp
981.LP
982.B "UNREF DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
983.br
984The directory inode \fII\fP was not connected to a directory entry
958.I Fsck_ffs
959exits.
960See a guru.
961.sp
962.LP
963.B "BAD STATE \fIS\fP FOR ROOT INODE"
964.br
965An internal error has caused an impossible state \fIS\fP to be assigned

--- 11 unchanged lines hidden (view full) ---

977and missing or full
978.I lost+found
979directories.
980.sp
981.LP
982.B "UNREF DIR I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
983.br
984The directory inode \fII\fP was not connected to a directory entry
985when the filesystem was traversed.
985when the file system was traversed.
986The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
987modify time \fIT\fP of directory inode \fII\fP are printed.
988When preen'ing, the directory is reconnected if its size is non-zero,
989otherwise it is cleared.
990.LP
991Possible responses to the RECONNECT prompt are:
992.IP YES
986The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
987modify time \fIT\fP of directory inode \fII\fP are printed.
988When preen'ing, the directory is reconnected if its size is non-zero,
989otherwise it is cleared.
990.LP
991Possible responses to the RECONNECT prompt are:
992.IP YES
993reconnect directory inode \fII\fP to the filesystem in the
993reconnect directory inode \fII\fP to the file system in the
994directory for lost files (usually \fIlost+found\fP).
995This may invoke the
996.I lost+found
997error condition in Phase 3
998if there are problems connecting directory inode \fII\fP to \fIlost+found\fP.
999This may also invoke the CONNECTED error condition in Phase 3 if the link
1000was successful.
1001.IP NO
1002ignore this error condition.
1003This will always invoke the UNREF error condition in Phase 4.
1004.sp
1005.LP
1006.B "NO lost+found DIRECTORY (CREATE)"
1007.br
1008There is no
1009.I lost+found
994directory for lost files (usually \fIlost+found\fP).
995This may invoke the
996.I lost+found
997error condition in Phase 3
998if there are problems connecting directory inode \fII\fP to \fIlost+found\fP.
999This may also invoke the CONNECTED error condition in Phase 3 if the link
1000was successful.
1001.IP NO
1002ignore this error condition.
1003This will always invoke the UNREF error condition in Phase 4.
1004.sp
1005.LP
1006.B "NO lost+found DIRECTORY (CREATE)"
1007.br
1008There is no
1009.I lost+found
1010directory in the root directory of the filesystem;
1010directory in the root directory of the file system;
1011When preen'ing
1012.I fsck_ffs
1013tries to create a \fIlost+found\fP directory.
1014.LP
1015Possible responses to the CREATE prompt are:
1016.IP YES
1011When preen'ing
1012.I fsck_ffs
1013tries to create a \fIlost+found\fP directory.
1014.LP
1015Possible responses to the CREATE prompt are:
1016.IP YES
1017create a \fIlost+found\fP directory in the root of the filesystem.
1017create a \fIlost+found\fP directory in the root of the file system.
1018This may raise the message:
1019.br
1020.B "NO SPACE LEFT IN / (EXPAND)"
1021.br
1022See below for the possible responses.
1023Inability to create a \fIlost+found\fP directory generates the message:
1024.br
1025.B "SORRY. CANNOT CREATE lost+found DIRECTORY"

--- 28 unchanged lines hidden (view full) ---

1054This will always invoke the UNREF error condition in Phase 4.
1055.sp
1056.LP
1057.B "NO SPACE LEFT IN /lost+found (EXPAND)"
1058.br
1059There is no space to add another entry to the
1060.I lost+found
1061directory in the root directory
1018This may raise the message:
1019.br
1020.B "NO SPACE LEFT IN / (EXPAND)"
1021.br
1022See below for the possible responses.
1023Inability to create a \fIlost+found\fP directory generates the message:
1024.br
1025.B "SORRY. CANNOT CREATE lost+found DIRECTORY"

--- 28 unchanged lines hidden (view full) ---

1054This will always invoke the UNREF error condition in Phase 4.
1055.sp
1056.LP
1057.B "NO SPACE LEFT IN /lost+found (EXPAND)"
1058.br
1059There is no space to add another entry to the
1060.I lost+found
1061directory in the root directory
1062of the filesystem.
1062of the file system.
1063When preen'ing the
1064.I lost+found
1065directory is expanded.
1066.LP
1067Possible responses to the EXPAND prompt are:
1068.IP YES
1069the
1070.I lost+found
1071directory is expanded to make room for the new entry.
1072If the attempted expansion fails
1073.I fsck_ffs
1074prints the message:
1075.br
1076.B "SORRY. NO SPACE IN lost+found DIRECTORY"
1077.br
1078and aborts the attempt to linkup the lost inode.
1079This will always invoke the UNREF error condition in Phase 4.
1080Clean out unnecessary entries in
1081.I lost+found .
1063When preen'ing the
1064.I lost+found
1065directory is expanded.
1066.LP
1067Possible responses to the EXPAND prompt are:
1068.IP YES
1069the
1070.I lost+found
1071directory is expanded to make room for the new entry.
1072If the attempted expansion fails
1073.I fsck_ffs
1074prints the message:
1075.br
1076.B "SORRY. NO SPACE IN lost+found DIRECTORY"
1077.br
1078and aborts the attempt to linkup the lost inode.
1079This will always invoke the UNREF error condition in Phase 4.
1080Clean out unnecessary entries in
1081.I lost+found .
1082This error is fatal if the filesystem is being preen'ed.
1082This error is fatal if the file system is being preen'ed.
1083.IP NO
1084abort the attempt to linkup the lost inode.
1085This will always invoke the UNREF error condition in Phase 4.
1086.sp
1087.LP
1088.B "DIR I=\fII1\fP CONNECTED. PARENT WAS I=\fII2\fP"
1089.br
1090This is an advisory message indicating a directory inode \fII1\fP was

--- 10 unchanged lines hidden (view full) ---

1101.br
1102A directory \fIF\fP has been found with size \fIS\fP that is not
1103a multiple of the directory blocksize \fIB\fP
1104(this can reoccur in Phase 3 if it is not adjusted in Phase 2).
1105.LP
1106Possible responses to the ADJUST prompt are:
1107.IP YES
1108the length is rounded up to the appropriate block size.
1083.IP NO
1084abort the attempt to linkup the lost inode.
1085This will always invoke the UNREF error condition in Phase 4.
1086.sp
1087.LP
1088.B "DIR I=\fII1\fP CONNECTED. PARENT WAS I=\fII2\fP"
1089.br
1090This is an advisory message indicating a directory inode \fII1\fP was

--- 10 unchanged lines hidden (view full) ---

1101.br
1102A directory \fIF\fP has been found with size \fIS\fP that is not
1103a multiple of the directory blocksize \fIB\fP
1104(this can reoccur in Phase 3 if it is not adjusted in Phase 2).
1105.LP
1106Possible responses to the ADJUST prompt are:
1107.IP YES
1108the length is rounded up to the appropriate block size.
1109This error can occur on 4.2BSD filesystems.
1110Thus when preen'ing the filesystem only a warning is printed
1109This error can occur on 4.2BSD file systems.
1110Thus when preen'ing the file system only a warning is printed
1111and the directory is adjusted.
1112.IP NO
1113ignore the error condition.
1114.sp
1115.LP
1116.B "BAD INODE \fIS\fP TO DESCEND"
1117.br
1118An internal error has caused an impossible state \fIS\fP to be passed to the
1111and the directory is adjusted.
1112.IP NO
1113ignore the error condition.
1114.sp
1115.LP
1116.B "BAD INODE \fIS\fP TO DESCEND"
1117.br
1118An internal error has caused an impossible state \fIS\fP to be passed to the
1119routine that descends the filesystem directory structure.
1119routine that descends the file system directory structure.
1120.I Fsck_ffs
1121exits.
1122See a guru.
1123.NH 2
1124Phase 4 \- Check Reference Counts
1125.PP
1126This phase concerns itself with the link count information
1127seen in Phase 2 and Phase 3.
1128This section lists error conditions resulting from
1129unreferenced files,
1130missing or full
1131.I lost+found
1132directory,
1133incorrect link counts for files, directories, symbolic links, or special files,
1134unreferenced files, symbolic links, and directories,
1135and bad or duplicate blocks in files, symbolic links, and directories.
1120.I Fsck_ffs
1121exits.
1122See a guru.
1123.NH 2
1124Phase 4 \- Check Reference Counts
1125.PP
1126This phase concerns itself with the link count information
1127seen in Phase 2 and Phase 3.
1128This section lists error conditions resulting from
1129unreferenced files,
1130missing or full
1131.I lost+found
1132directory,
1133incorrect link counts for files, directories, symbolic links, or special files,
1134unreferenced files, symbolic links, and directories,
1135and bad or duplicate blocks in files, symbolic links, and directories.
1136All errors in this phase are correctable if the filesystem is being preen'ed
1136All errors in this phase are correctable if the file system is being preen'ed
1137except running out of space in the \fIlost+found\fP directory.
1138.sp
1139.LP
1140.B "UNREF FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
1141.br
1142Inode \fII\fP was not connected to a directory entry
1137except running out of space in the \fIlost+found\fP directory.
1138.sp
1139.LP
1140.B "UNREF FILE I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (RECONNECT)"
1141.br
1142Inode \fII\fP was not connected to a directory entry
1143when the filesystem was traversed.
1143when the file system was traversed.
1144The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
1145modify time \fIT\fP of inode \fII\fP are printed.
1146When preen'ing the file is cleared if either its size or its
1147link count is zero,
1148otherwise it is reconnected.
1149.LP
1150Possible responses to the RECONNECT prompt are:
1151.IP YES
1144The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and
1145modify time \fIT\fP of inode \fII\fP are printed.
1146When preen'ing the file is cleared if either its size or its
1147link count is zero,
1148otherwise it is reconnected.
1149.LP
1150Possible responses to the RECONNECT prompt are:
1151.IP YES
1152reconnect inode \fII\fP to the filesystem in the directory for
1152reconnect inode \fII\fP to the file system in the directory for
1153lost files (usually \fIlost+found\fP).
1154This may invoke the
1155.I lost+found
1156error condition in Phase 4
1157if there are problems connecting inode \fII\fP to
1158.I lost+found .
1159.IP NO
1160ignore this error condition.
1161This will always invoke the CLEAR error condition in Phase 4.
1162.sp
1163.LP
1164.B "(CLEAR)"
1165.br
1166The inode mentioned in the immediately previous error condition can not be
1167reconnected.
1153lost files (usually \fIlost+found\fP).
1154This may invoke the
1155.I lost+found
1156error condition in Phase 4
1157if there are problems connecting inode \fII\fP to
1158.I lost+found .
1159.IP NO
1160ignore this error condition.
1161This will always invoke the CLEAR error condition in Phase 4.
1162.sp
1163.LP
1164.B "(CLEAR)"
1165.br
1166The inode mentioned in the immediately previous error condition can not be
1167reconnected.
1168This cannot occur if the filesystem is being preen'ed,
1168This cannot occur if the file system is being preen'ed,
1169since lack of space to reconnect files is a fatal error.
1170.LP
1171Possible responses to the CLEAR prompt are:
1172.IP YES
1173de-allocate the inode mentioned in the immediately previous error condition by zeroing its contents.
1174.IP NO
1175ignore this error condition.
1176.sp
1177.LP
1178.B "NO lost+found DIRECTORY (CREATE)"
1179.br
1180There is no
1181.I lost+found
1169since lack of space to reconnect files is a fatal error.
1170.LP
1171Possible responses to the CLEAR prompt are:
1172.IP YES
1173de-allocate the inode mentioned in the immediately previous error condition by zeroing its contents.
1174.IP NO
1175ignore this error condition.
1176.sp
1177.LP
1178.B "NO lost+found DIRECTORY (CREATE)"
1179.br
1180There is no
1181.I lost+found
1182directory in the root directory of the filesystem;
1182directory in the root directory of the file system;
1183When preen'ing
1184.I fsck_ffs
1185tries to create a \fIlost+found\fP directory.
1186.LP
1187Possible responses to the CREATE prompt are:
1188.IP YES
1183When preen'ing
1184.I fsck_ffs
1185tries to create a \fIlost+found\fP directory.
1186.LP
1187Possible responses to the CREATE prompt are:
1188.IP YES
1189create a \fIlost+found\fP directory in the root of the filesystem.
1189create a \fIlost+found\fP directory in the root of the file system.
1190This may raise the message:
1191.br
1192.B "NO SPACE LEFT IN / (EXPAND)"
1193.br
1194See below for the possible responses.
1195Inability to create a \fIlost+found\fP directory generates the message:
1196.br
1197.B "SORRY. CANNOT CREATE lost+found DIRECTORY"

--- 28 unchanged lines hidden (view full) ---

1226This will always invoke the UNREF error condition in Phase 4.
1227.sp
1228.LP
1229.B "NO SPACE LEFT IN /lost+found (EXPAND)"
1230.br
1231There is no space to add another entry to the
1232.I lost+found
1233directory in the root directory
1190This may raise the message:
1191.br
1192.B "NO SPACE LEFT IN / (EXPAND)"
1193.br
1194See below for the possible responses.
1195Inability to create a \fIlost+found\fP directory generates the message:
1196.br
1197.B "SORRY. CANNOT CREATE lost+found DIRECTORY"

--- 28 unchanged lines hidden (view full) ---

1226This will always invoke the UNREF error condition in Phase 4.
1227.sp
1228.LP
1229.B "NO SPACE LEFT IN /lost+found (EXPAND)"
1230.br
1231There is no space to add another entry to the
1232.I lost+found
1233directory in the root directory
1234of the filesystem.
1234of the file system.
1235When preen'ing the
1236.I lost+found
1237directory is expanded.
1238.LP
1239Possible responses to the EXPAND prompt are:
1240.IP YES
1241the
1242.I lost+found
1243directory is expanded to make room for the new entry.
1244If the attempted expansion fails
1245.I fsck_ffs
1246prints the message:
1247.br
1248.B "SORRY. NO SPACE IN lost+found DIRECTORY"
1249.br
1250and aborts the attempt to linkup the lost inode.
1251This will always invoke the UNREF error condition in Phase 4.
1252Clean out unnecessary entries in
1253.I lost+found .
1235When preen'ing the
1236.I lost+found
1237directory is expanded.
1238.LP
1239Possible responses to the EXPAND prompt are:
1240.IP YES
1241the
1242.I lost+found
1243directory is expanded to make room for the new entry.
1244If the attempted expansion fails
1245.I fsck_ffs
1246prints the message:
1247.br
1248.B "SORRY. NO SPACE IN lost+found DIRECTORY"
1249.br
1250and aborts the attempt to linkup the lost inode.
1251This will always invoke the UNREF error condition in Phase 4.
1252Clean out unnecessary entries in
1253.I lost+found .
1254This error is fatal if the filesystem is being preen'ed.
1254This error is fatal if the file system is being preen'ed.
1255.IP NO
1256abort the attempt to linkup the lost inode.
1257This will always invoke the UNREF error condition in Phase 4.
1258.sp
1259.LP
1260.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)"
1261.br
1262The link count for inode \fII\fP,

--- 14 unchanged lines hidden (view full) ---

1277replace the link count of file inode \fII\fP with \fIY\fP.
1278.IP NO
1279ignore this error condition.
1280.sp
1281.LP
1282.B "UNREF \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1283.br
1284Inode \fII\fP, was not connected to a directory entry when the
1255.IP NO
1256abort the attempt to linkup the lost inode.
1257This will always invoke the UNREF error condition in Phase 4.
1258.sp
1259.LP
1260.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)"
1261.br
1262The link count for inode \fII\fP,

--- 14 unchanged lines hidden (view full) ---

1277replace the link count of file inode \fII\fP with \fIY\fP.
1278.IP NO
1279ignore this error condition.
1280.sp
1281.LP
1282.B "UNREF \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1283.br
1284Inode \fII\fP, was not connected to a directory entry when the
1285filesystem was traversed.
1285file system was traversed.
1286The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1287and modify time \fIT\fP of inode \fII\fP
1288are printed.
1289When preen'ing,
1290this is a file that was not connected because its size or link count was zero,
1291hence it is cleared.
1292.LP
1293Possible responses to the CLEAR prompt are:

--- 6 unchanged lines hidden (view full) ---

1300.B "BAD/DUP \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1301.br
1302Phase 1 or Phase 1b have found duplicate blocks
1303or bad blocks associated with
1304inode \fII\fP.
1305The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1306and modify time \fIT\fP of inode \fII\fP
1307are printed.
1286The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1287and modify time \fIT\fP of inode \fII\fP
1288are printed.
1289When preen'ing,
1290this is a file that was not connected because its size or link count was zero,
1291hence it is cleared.
1292.LP
1293Possible responses to the CLEAR prompt are:

--- 6 unchanged lines hidden (view full) ---

1300.B "BAD/DUP \fItype\fP I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP (CLEAR)"
1301.br
1302Phase 1 or Phase 1b have found duplicate blocks
1303or bad blocks associated with
1304inode \fII\fP.
1305The owner \fIO\fP, mode \fIM\fP, size \fIS\fP,
1306and modify time \fIT\fP of inode \fII\fP
1307are printed.
1308This error cannot arise when the filesystem is being preen'ed,
1308This error cannot arise when the file system is being preen'ed,
1309as it would have caused a fatal error earlier.
1310.LP
1311Possible responses to the CLEAR prompt are:
1312.IP YES
1313de-allocate inode \fII\fP by zeroing its contents.
1314.IP NO
1315ignore this error condition.
1316.NH 2

--- 11 unchanged lines hidden (view full) ---

1328.sp
1329.LP
1330.B "CG \fIC\fP: BAD MAGIC NUMBER"
1331.br
1332The magic number of cylinder group \fIC\fP is wrong.
1333This usually indicates that the cylinder group maps have been destroyed.
1334When running manually the cylinder group is marked as needing
1335to be reconstructed.
1309as it would have caused a fatal error earlier.
1310.LP
1311Possible responses to the CLEAR prompt are:
1312.IP YES
1313de-allocate inode \fII\fP by zeroing its contents.
1314.IP NO
1315ignore this error condition.
1316.NH 2

--- 11 unchanged lines hidden (view full) ---

1328.sp
1329.LP
1330.B "CG \fIC\fP: BAD MAGIC NUMBER"
1331.br
1332The magic number of cylinder group \fIC\fP is wrong.
1333This usually indicates that the cylinder group maps have been destroyed.
1334When running manually the cylinder group is marked as needing
1335to be reconstructed.
1336This error is fatal if the filesystem is being preen'ed.
1336This error is fatal if the file system is being preen'ed.
1337.sp
1338.LP
1339.B "BLK(S) MISSING IN BIT MAPS (SALVAGE)"
1340.br
1341A cylinder group block map is missing some free blocks.
1342During preen'ing the maps are reconstructed.
1343.LP
1344Possible responses to the SALVAGE prompt are:

--- 25 unchanged lines hidden (view full) ---

1370Possible responses to the SALVAGE prompt are:
1371.IP YES
1372reconstruct the superblock free block information.
1373.IP NO
1374ignore this error condition.
1375.NH 2
1376Cleanup
1377.PP
1337.sp
1338.LP
1339.B "BLK(S) MISSING IN BIT MAPS (SALVAGE)"
1340.br
1341A cylinder group block map is missing some free blocks.
1342During preen'ing the maps are reconstructed.
1343.LP
1344Possible responses to the SALVAGE prompt are:

--- 25 unchanged lines hidden (view full) ---

1370Possible responses to the SALVAGE prompt are:
1371.IP YES
1372reconstruct the superblock free block information.
1373.IP NO
1374ignore this error condition.
1375.NH 2
1376Cleanup
1377.PP
1378Once a filesystem has been checked, a few cleanup functions are performed.
1378Once a file system has been checked, a few cleanup functions are performed.
1379This section lists advisory messages about
1379This section lists advisory messages about
1380the filesystem
1381and modify status of the filesystem.
1380the file system
1381and modify status of the file system.
1382.sp
1383.LP
1384.B "\fIV\fP files, \fIW\fP used, \fIX\fP free (\fIY\fP frags, \fIZ\fP blocks)"
1385.br
1386This is an advisory message indicating that
1382.sp
1383.LP
1384.B "\fIV\fP files, \fIW\fP used, \fIX\fP free (\fIY\fP frags, \fIZ\fP blocks)"
1385.br
1386This is an advisory message indicating that
1387the filesystem checked contained
1387the file system checked contained
1388\fIV\fP files using
1389\fIW\fP fragment sized blocks leaving
1388\fIV\fP files using
1389\fIW\fP fragment sized blocks leaving
1390\fIX\fP fragment sized blocks free in the filesystem.
1390\fIX\fP fragment sized blocks free in the file system.
1391The numbers in parenthesis breaks the free count down into
1392\fIY\fP free fragments and
1393\fIZ\fP free full sized blocks.
1394.sp
1395.LP
1396.B "***** REBOOT UNIX *****"
1397.br
1398This is an advisory message indicating that
1391The numbers in parenthesis breaks the free count down into
1392\fIY\fP free fragments and
1393\fIZ\fP free full sized blocks.
1394.sp
1395.LP
1396.B "***** REBOOT UNIX *****"
1397.br
1398This is an advisory message indicating that
1399the root filesystem has been modified by
1399the root file system has been modified by
1400.I fsck_ffs.
1401If UNIX is not rebooted immediately,
1402the work done by
1403.I fsck_ffs
1404may be undone by the in-core copies of tables
1405UNIX keeps.
1406When preen'ing,
1407.I fsck_ffs
1408will exit with a code of 4.
1409The standard auto-reboot script distributed with 4.3BSD
1410interprets an exit code of 4 by issuing a reboot system call.
1411.sp
1412.LP
1413.B "***** FILE SYSTEM WAS MODIFIED *****"
1414.br
1415This is an advisory message indicating that
1400.I fsck_ffs.
1401If UNIX is not rebooted immediately,
1402the work done by
1403.I fsck_ffs
1404may be undone by the in-core copies of tables
1405UNIX keeps.
1406When preen'ing,
1407.I fsck_ffs
1408will exit with a code of 4.
1409The standard auto-reboot script distributed with 4.3BSD
1410interprets an exit code of 4 by issuing a reboot system call.
1411.sp
1412.LP
1413.B "***** FILE SYSTEM WAS MODIFIED *****"
1414.br
1415This is an advisory message indicating that
1416the current filesystem was modified by
1416the current file system was modified by
1417.I fsck_ffs.
1417.I fsck_ffs.
1418If this filesystem is mounted or is the current root filesystem,
1418If this file system is mounted or is the current root file system,
1419.I fsck_ffs
1420should be halted and UNIX rebooted.
1421If UNIX is not rebooted immediately,
1422the work done by
1423.I fsck_ffs
1424may be undone by the in-core copies of tables
1425UNIX keeps.
1419.I fsck_ffs
1420should be halted and UNIX rebooted.
1421If UNIX is not rebooted immediately,
1422the work done by
1423.I fsck_ffs
1424may be undone by the in-core copies of tables
1425UNIX keeps.