Lines Matching +full:continue +full:- +full:on +full:- +full:error

23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30 Appendix A \- Fsck_ffs Error Conditions
36 a multi-pass file system check program.
44 path-names,
53 is run non-interactively to
66 reports the error condition to the operator.
74 This appendix explains the meaning of each error condition,
75 the possible responses, and the related error conditions.
77 The error conditions are organized by the
82 The error conditions that may occur
92 This section lists error conditions resulting from
107 legal options are \-b, \-c, \-y, \-n, and \-p.
109 terminates on this error condition.
128 terminates on this error condition.
139 terminates on this error condition.
149 terminates on this error condition.
176 Either the \-n flag was specified or
193 ignore this error condition.
211 ignore this error condition.
225 ignore this error condition.
236 ignore this error condition.
248 ignore this error condition.
269 .B "USE -b OPTION TO FSCK_FFS TO SPECIFY LOCATION OF AN ALTERNATE"
271 .B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck_ffs(8)."
279 specifying \-b 32 is a good first choice.
290 .B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)"
298 Possible responses to the CONTINUE prompt are:
300 attempt to continue to run the file system check.
303 This error condition will not allow a complete check of the file system.
306 should be made to re-check this file system.
310 will terminate with the message ``Fatal I/O error''.
315 .B "CAN NOT READ: BLK \fIB\fP (CONTINUE)"
323 Possible responses to the CONTINUE prompt are:
325 attempt to continue to run the file system check.
333 ever tries to write back one of the blocks on which the read failed
340 This error condition will not allow a complete check of the file system.
343 should be made to re-check this file system.
347 will terminate with the message ``Fatal I/O error''.
352 .B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)"
357 The disk is write-protected;
358 check the write protect lock on the drive.
361 Possible responses to the CONTINUE prompt are:
363 attempt to continue to run the file system check.
371 This error condition will not allow a complete check of the file system.
374 should be made to re-check this file system.
378 will terminate with the message ``Fatal I/O error''.
385 An internal error has attempted to read non-existent inode \fIDDD\fP.
386 This error causes 
391 Phase 1 \- Check Blocks and Sizes
395 This section lists error conditions resulting from
397 setting up the zero-link-count table,
416 de-allocate inode \fII\fP by zeroing its contents.
417 This will always invoke the UNALLOCATED error condition in Phase 2
420 ignore this error condition.
438 ignore this error condition.
441 .B "LINK COUNT TABLE OVERFLOW (CONTINUE)"
450 Possible responses to the CONTINUE prompt are:
452 continue with the program.
453 This error condition will not allow a complete check of the file system.
456 should be made to re-check this file system.
458 this error condition is repeated.
469 This error condition may invoke the
471 error condition in Phase 1 (see next paragraph) if
473 This error condition will always invoke the
475 error condition in Phase 2 and Phase 4.
478 .B "EXCESSIVE BAD BLKS I=\fII\fP (CONTINUE)"
484 Possible responses to the CONTINUE prompt are:
487 and continue checking with the next inode in the file system.
488 This error condition will not allow a complete check of the file system.
491 should be made to re-check this file system.
498 An internal error has scrambled 
510 This error condition may invoke the
512 error condition in Phase 1 if
514 This error condition will always invoke Phase 1b and the
516 error condition in Phase 2 and Phase 4.
519 .B "EXCESSIVE DUP BLKS I=\fII\fP (CONTINUE)"
524 Possible responses to the CONTINUE prompt are:
527 and continue checking with the next inode in the file system.
528 This error condition will not allow a complete check of the file system.
531 should be made to re-check this file system.
536 .B "DUP TABLE OVERFLOW (CONTINUE)"
544 Possible responses to the CONTINUE prompt are:
546 continue with the program.
547 This error condition will not allow a complete check of the file system.
550 should be made to re-check this file system.
551 If another duplicate block is found, this error condition will repeat.
562 de-allocate inode \fII\fP by zeroing its contents.
564 ignore this error condition.
577 ignore this error condition.
583 This section lists the error condition when the duplicate block is found.
590 This error condition will always invoke the
592 error condition in Phase 2.
594 this error condition and the DUP error condition in Phase 1.
596 Phase 2 \- Check Pathnames
600 error conditioned inodes
602 This section lists error conditions resulting from
659 many error conditions will be produced.
684 .B "CONTINUE" .
686 Possible responses to the CONTINUE prompt are:
690 error condition in the root inode and
691 attempt to continue to run the file system check.
693 then this may result in many other error conditions.
715 ignore this error condition.
728 ignore this error condition.
742 ignore this error condition.
754 this will always invoke the BAD/DUP error condition in Phase 4.
756 ignore this error condition.
781 This error can occur on 4.2BSD file systems.
785 ignore the error condition.
794 throw away all entries up to the next directory boundary (usually 512-byte)
935 ignore the error condition.
940 An internal error has caused an impossible state \fIS\fP to be passed to the
949 An internal error has caused an impossible state \fIS\fP to be returned
958 An internal error has caused an impossible state \fIS\fP to be assigned
964 Phase 3 \- Check Connectivity
968 This section lists error conditions resulting from
981 When preen'ing, the directory is reconnected if its size is non-zero,
990 error condition in Phase 3
992 This may also invoke the CONNECTED error condition in Phase 3 if the link
995 ignore this error condition.
996 This will always invoke the UNREF error condition in Phase 4.
1021 This will always invoke the UNREF error condition in Phase 4.
1024 This will always invoke the UNREF error condition in Phase 4.
1044 This will always invoke the UNREF error condition in Phase 4.
1047 This will always invoke the UNREF error condition in Phase 4.
1072 This will always invoke the UNREF error condition in Phase 4.
1075 This error is fatal if the file system is being preen'ed.
1078 This will always invoke the UNREF error condition in Phase 4.
1102 This error can occur on 4.2BSD file systems.
1106 ignore the error condition.
1111 An internal error has caused an impossible state \fIS\fP to be passed to the
1117 Phase 4 \- Check Reference Counts
1121 This section lists error conditions resulting from
1149 error condition in Phase 4
1153 ignore this error condition.
1154 This will always invoke the CLEAR error condition in Phase 4.
1159 The inode mentioned in the immediately previous error condition can not be
1162 since lack of space to reconnect files is a fatal error.
1166 de-allocate the inode mentioned in the immediately previous error condition by zeroing its contents.
1168 ignore this error condition.
1193 This will always invoke the UNREF error condition in Phase 4.
1196 This will always invoke the UNREF error condition in Phase 4.
1216 This will always invoke the UNREF error condition in Phase 4.
1219 This will always invoke the UNREF error condition in Phase 4.
1244 This will always invoke the UNREF error condition in Phase 4.
1247 This error is fatal if the file system is being preen'ed.
1250 This will always invoke the UNREF error condition in Phase 4.
1272 ignore this error condition.
1288 de-allocate inode \fII\fP by zeroing its contents.
1290 ignore this error condition.
1301 This error cannot arise when the file system is being preen'ed,
1302 as it would have caused a fatal error earlier.
1306 de-allocate inode \fII\fP by zeroing its contents.
1308 ignore this error condition.
1310 Phase 5 - Check Cyl groups
1312 This phase concerns itself with the free-block and used-inode maps.
1313 This section lists error conditions resulting from
1314 allocated blocks in the free-block maps,
1315 free blocks missing from free-block maps,
1316 and the total free-block count incorrect.
1317 It also lists error conditions resulting from
1318 free inodes in the used-inode maps,
1319 allocated inodes missing from used-inode maps,
1320 and the total used-inode count incorrect.
1329 This error is fatal if the file system is being preen'ed.
1341 ignore this error condition.
1354 ignore this error condition.
1367 ignore this error condition.
1397 may be undone by the in-core copies of tables
1402 The standard auto-reboot script distributed with 4.3BSD 
1417 may be undone by the in-core copies of tables