| 4.t (1558) | 4.t (66861) |
|---|---|
| 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 66861 2000-10-09 08:26:35Z adrian $ |
|
| 32.\" @(#)4.t 8.1 (Berkeley) 6/5/93 33.\" | 33.\" @(#)4.t 8.1 (Berkeley) 6/5/93 34.\" |
| 34.ds RH Appendix A \- Fsck Error Conditions | 35.ds RH Appendix A \- Fsck_ffs Error Conditions |
| 35.NH | 36.NH |
| 36Appendix A \- Fsck Error Conditions | 37Appendix A \- Fsck_ffs Error Conditions |
| 37.NH 2 38Conventions 39.PP | 38.NH 2 39Conventions 40.PP |
| 40.I Fsck | 41.I Fsck_ffs |
| 41is 42a multi-pass file system check program. 43Each file system pass invokes a different Phase of the | 42is 43a multi-pass file system check program. 44Each file system pass invokes a different Phase of the |
| 44.I fsck | 45.I fsck_ffs |
| 45program. 46After the initial setup, | 46program. 47After the initial setup, |
| 47.I fsck | 48.I fsck_ffs |
| 48performs successive Phases over each file system, 49checking blocks and sizes, 50path-names, 51connectivity, 52reference counts, 53and the map of free blocks, 54(possibly rebuilding it), 55and performs some cleanup. 56.LP 57Normally | 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 |
| 58.I fsck | 59.I fsck_ffs |
| 59is run non-interactively to 60.I preen 61the file systems after an unclean halt. 62While preen'ing a file system, 63it will only fix corruptions that are expected 64to occur from an unclean halt. 65These actions are a proper subset of the actions that | 60is run non-interactively to 61.I preen 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 |
| 66.I fsck | 67.I fsck_ffs |
| 67will take when it is running interactively. 68Throughout this appendix many errors have several options 69that the operator can take. 70When an inconsistency is detected, | 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, |
| 71.I fsck | 72.I fsck_ffs |
| 72reports the error condition to the operator. 73If a response is required, | 73reports the error condition to the operator. 74If a response is required, |
| 74.I fsck | 75.I fsck_ffs |
| 75prints a prompt message and 76waits for a response. 77When preen'ing most errors are fatal. 78For those that are expected, 79the response taken is noted. 80This appendix explains the meaning of each error condition, 81the possible responses, and the related error conditions. 82.LP 83The error conditions are organized by the 84.I Phase 85of the | 76prints a prompt message and 77waits for a response. 78When preen'ing most errors are fatal. 79For those that are expected, 80the response taken is noted. 81This appendix explains the meaning of each error condition, 82the possible responses, and the related error conditions. 83.LP 84The error conditions are organized by the 85.I Phase 86of the |
| 86.I fsck | 87.I fsck_ffs |
| 87program in which they can occur. 88The error conditions that may occur 89in more than one Phase 90will be discussed in initialization. 91.NH 2 92Initialization 93.PP 94Before a file system check can be performed, certain --- 9 unchanged lines hidden (view full) --- 104and creation of the scratch file. 105All the initialization errors are fatal 106when the file system is being preen'ed. 107.sp 108.LP 109.B "\fIC\fP option?" 110.br 111\fIC\fP is not a legal option to | 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 file system check can be performed, certain --- 9 unchanged lines hidden (view full) --- 105and creation of the scratch file. 106All the initialization errors are fatal 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 |
| 112.I fsck ; | 113.I fsck_ffs ; |
| 113legal options are \-b, \-c, \-y, \-n, and \-p. | 114legal options are \-b, \-c, \-y, \-n, and \-p. |
| 114.I Fsck | 115.I Fsck_ffs |
| 115terminates on this error condition. 116See the | 116terminates on this error condition. 117See the |
| 117.I fsck (8) | 118.I fsck_ffs (8) |
| 118manual entry for further detail. 119.sp 120.LP 121.B "cannot alloc NNN bytes for blockmap" 122.br 123.B "cannot alloc NNN bytes for freemap" 124.br 125.B "cannot alloc NNN bytes for statemap" 126.br 127.B "cannot alloc NNN bytes for lncntp" 128.br | 119manual entry for further detail. 120.sp 121.LP 122.B "cannot alloc NNN bytes for blockmap" 123.br 124.B "cannot alloc NNN bytes for freemap" 125.br 126.B "cannot alloc NNN bytes for statemap" 127.br 128.B "cannot alloc NNN bytes for lncntp" 129.br |
| 129.I Fsck 's | 130.I Fsck_ffs 's |
| 130request for memory for its virtual 131memory tables failed. 132This should never happen. | 131request for memory for its virtual 132memory tables failed. 133This should never happen. |
| 133.I Fsck | 134.I Fsck_ffs |
| 134terminates on this error condition. 135See a guru. 136.sp 137.LP 138.B "Can't open checklist file: \fIF\fP" 139.br 140The file system checklist file 141\fIF\fP (usually 142.I /etc/fstab ) 143can not be opened for reading. | 135terminates on this error condition. 136See a guru. 137.sp 138.LP 139.B "Can't open checklist file: \fIF\fP" 140.br 141The file system checklist file 142\fIF\fP (usually 143.I /etc/fstab ) 144can not be opened for reading. |
| 144.I Fsck | 145.I Fsck_ffs |
| 145terminates on this error condition. 146Check access modes of \fIF\fP. 147.sp 148.LP 149.B "Can't stat root" 150.br | 146terminates on this error condition. 147Check access modes of \fIF\fP. 148.sp 149.LP 150.B "Can't stat root" 151.br |
| 151.I Fsck 's | 152.I Fsck_ffs 's |
| 152request for statistics about the root directory ``/'' failed. 153This should never happen. | 153request for statistics about the root directory ``/'' failed. 154This should never happen. |
| 154.I Fsck | 155.I Fsck_ffs |
| 155terminates on this error condition. 156See a guru. 157.sp 158.LP 159.B "Can't stat \fIF\fP" 160.br 161.B "Can't make sense out of name \fIF\fP" 162.br | 156terminates on this error condition. 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 |
| 163.I Fsck 's | 164.I Fsck_ffs 's |
| 164request for statistics about the file system \fIF\fP failed. 165When running manually, 166it ignores this file system 167and continues checking the next file system given. 168Check access modes of \fIF\fP. 169.sp 170.LP 171.B "Can't open \fIF\fP" 172.br | 165request for statistics about the file system \fIF\fP failed. 166When running manually, 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 |
| 173.I Fsck 's | 174.I Fsck_ffs 's |
| 174request attempt to open the file system \fIF\fP failed. 175When running manually, it ignores this file system 176and continues checking the next file system given. 177Check access modes of \fIF\fP. 178.sp 179.LP 180.B "\fIF\fP: (NO WRITE)" 181.br 182Either the \-n flag was specified or | 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 |
| 183.I fsck 's | 184.I fsck_ffs 's |
| 184attempt to open the file system \fIF\fP for writing failed. 185When running manually, 186all the diagnostics are printed out, 187but no modifications are attempted to fix them. 188.sp 189.LP 190.B "file is not a block or character device; OK" 191.br 192You have given | 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 |
| 193.I fsck | 194.I fsck_ffs |
| 194a regular file name by mistake. 195Check the type of the file specified. 196.LP 197Possible responses to the OK prompt are: 198.IP YES 199ignore this error condition. 200.IP NO 201ignore this file system and continues checking --- 65 unchanged lines hidden (view full) --- 267.B "SIZE PREPOSTEROUSLY LARGE" 268.br 269.B "TRASHED VALUES IN SUPER BLOCK" 270.br 271and will be followed by the message: 272.br 273.B "\fIF\fP: BAD SUPER BLOCK: \fIB\fP" 274.br | 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 file system and continues checking --- 65 unchanged lines hidden (view full) --- 268.B "SIZE PREPOSTEROUSLY LARGE" 269.br 270.B "TRASHED VALUES IN SUPER BLOCK" 271.br 272and will be followed by the message: 273.br 274.B "\fIF\fP: BAD SUPER BLOCK: \fIB\fP" 275.br |
| 275.B "USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE" | 276.B "USE -b OPTION TO FSCK_FFS TO SPECIFY LOCATION OF AN ALTERNATE" |
| 276.br | 277.br |
| 277.B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8)." | 278.B "SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck_ffs(8)." |
| 278.br 279The super block has been corrupted. 280An alternative super block must be selected from among those 281listed by 282.I newfs 283(8) when the file system was created. 284For file systems with a blocksize less than 32K, 285specifying \-b 32 is a good first choice. 286.sp 287.LP 288.B "INTERNAL INCONSISTENCY: \fIM\fP" 289.br | 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 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 |
| 290.I Fsck 's | 291.I Fsck_ffs 's |
| 291has had an internal panic, whose message is specified as \fIM\fP. 292This should never happen. 293See a guru. 294.sp 295.LP 296.B "CAN NOT SEEK: BLK \fIB\fP (CONTINUE)" 297.br | 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 |
| 298.I Fsck 's | 299.I Fsck_ffs 's |
| 299request for moving to a specified block number \fIB\fP in 300the file system failed. 301This should never happen. 302See a guru. 303.LP 304Possible responses to the CONTINUE prompt are: 305.IP YES 306attempt to continue to run the file system check. 307Often, 308however the problem will persist. 309This error condition will not allow a complete check of the file system. 310A second run of | 300request for moving to a specified block number \fIB\fP in 301the file system failed. 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 file system check. 308Often, 309however the problem will persist. 310This error condition will not allow a complete check of the file system. 311A second run of |
| 311.I fsck | 312.I fsck_ffs |
| 312should be made to re-check this file system. 313If the block was part of the virtual memory buffer 314cache, | 313should be made to re-check this file system. 314If the block was part of the virtual memory buffer 315cache, |
| 315.I fsck | 316.I fsck_ffs |
| 316will terminate with the message ``Fatal I/O error''. 317.IP NO 318terminate the program. 319.sp 320.LP 321.B "CAN NOT READ: BLK \fIB\fP (CONTINUE)" 322.br | 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 |
| 323.I Fsck 's | 324.I Fsck_ffs 's |
| 324request for reading a specified block number \fIB\fP in 325the file system failed. 326This should never happen. 327See a guru. 328.LP 329Possible responses to the CONTINUE prompt are: 330.IP YES 331attempt to continue to run the file system check. 332It will retry the read and print out the message: 333.br 334.B "THE FOLLOWING SECTORS COULD NOT BE READ: \fIN\fP" 335.br 336where \fIN\fP indicates the sectors that could not be read. 337If | 325request for reading a specified block number \fIB\fP in 326the file system failed. 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 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 |
| 338.I fsck | 339.I fsck_ffs |
| 339ever tries to write back one of the blocks on which the read failed 340it will print the message: 341.br 342.B "WRITING ZERO'ED BLOCK \fIN\fP TO DISK" 343.br 344where \fIN\fP indicates the sector that was written with zero's. 345If the disk is experiencing hardware problems, the problem will persist. 346This error condition will not allow a complete check of the file system. 347A second run of | 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 file system. 348A second run of |
| 348.I fsck | 349.I fsck_ffs |
| 349should be made to re-check this file system. 350If the block was part of the virtual memory buffer 351cache, | 350should be made to re-check this file system. 351If the block was part of the virtual memory buffer 352cache, |
| 352.I fsck | 353.I fsck_ffs |
| 353will terminate with the message ``Fatal I/O error''. 354.IP NO 355terminate the program. 356.sp 357.LP 358.B "CAN NOT WRITE: BLK \fIB\fP (CONTINUE)" 359.br | 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 |
| 360.I Fsck 's | 361.I Fsck_ffs 's |
| 361request for writing a specified block number \fIB\fP 362in the file system failed. 363The disk is write-protected; 364check the write protect lock on the drive. 365If that is not the problem, see a guru. 366.LP 367Possible responses to the CONTINUE prompt are: 368.IP YES 369attempt to continue to run the file system check. 370The write operation will be retried with the failed blocks 371indicated by the message: 372.br 373.B "THE FOLLOWING SECTORS COULD NOT BE WRITTEN: \fIN\fP" 374.br 375where \fIN\fP indicates the sectors that could not be written. 376If the disk is experiencing hardware problems, the problem will persist. 377This error condition will not allow a complete check of the file system. 378A second run of | 362request for writing a specified block number \fIB\fP 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 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. 378This error condition will not allow a complete check of the file system. 379A second run of |
| 379.I fsck | 380.I fsck_ffs |
| 380should be made to re-check this file system. 381If the block was part of the virtual memory buffer 382cache, | 381should be made to re-check this file system. 382If the block was part of the virtual memory buffer 383cache, |
| 383.I fsck | 384.I fsck_ffs |
| 384will terminate with the message ``Fatal I/O error''. 385.IP NO 386terminate the program. 387.sp 388.LP 389.B "bad inode number DDD to ginode" 390.br 391An internal error has attempted to read non-existent inode \fIDDD\fP. 392This error causes | 385will terminate with the message ``Fatal I/O error''. 386.IP NO 387terminate the program. 388.sp 389.LP 390.B "bad inode number DDD to ginode" 391.br 392An internal error has attempted to read non-existent inode \fIDDD\fP. 393This error causes |
| 393.I fsck | 394.I fsck_ffs |
| 394to exit. 395See a guru. 396.NH 2 397Phase 1 \- Check Blocks and Sizes 398.PP 399This phase concerns itself with 400the inode list. 401This section lists error conditions resulting from --- 21 unchanged lines hidden (view full) --- 423This will always invoke the UNALLOCATED error condition in Phase 2 424for each directory entry pointing to this inode. 425.IP NO 426ignore this error condition. 427.sp 428.LP 429.B "PARTIALLY TRUNCATED INODE I=\fII\fP (SALVAGE)" 430.br | 395to exit. 396See a guru. 397.NH 2 398Phase 1 \- Check Blocks and Sizes 399.PP 400This phase concerns itself with 401the inode list. 402This section lists error conditions resulting from --- 21 unchanged lines hidden (view full) --- 424This will always invoke the UNALLOCATED error condition in Phase 2 425for each directory entry pointing to this inode. 426.IP NO 427ignore this error condition. 428.sp 429.LP 430.B "PARTIALLY TRUNCATED INODE I=\fII\fP (SALVAGE)" 431.br |
| 431.I Fsck | 432.I Fsck_ffs |
| 432has found inode \fII\fP whose size is shorter than the number of 433blocks allocated to it. 434This condition should only occur if the system crashes while in the 435midst of truncating a file. 436When preen'ing the file system, | 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 file system, |
| 437.I fsck | 438.I fsck_ffs |
| 438completes the truncation to the specified size. 439.LP 440Possible responses to SALVAGE are: 441.IP YES 442complete the truncation to the size specified in the inode. 443.IP NO 444ignore this error condition. 445.sp 446.LP 447.B "LINK COUNT TABLE OVERFLOW (CONTINUE)" 448.br 449An internal table for | 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. 446.sp 447.LP 448.B "LINK COUNT TABLE OVERFLOW (CONTINUE)" 449.br 450An internal table for |
| 450.I fsck | 451.I fsck_ffs |
| 451containing allocated inodes with a link count of 452zero cannot allocate more memory. 453Increase the virtual memory for | 452containing allocated inodes with a link count of 453zero cannot allocate more memory. 454Increase the virtual memory for |
| 454.I fsck . | 455.I fsck_ffs . |
| 455.LP 456Possible responses to the CONTINUE prompt are: 457.IP YES 458continue with the program. 459This error condition will not allow a complete check of the file system. 460A second run of | 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 file system. 461A second run of |
| 461.I fsck | 462.I fsck_ffs |
| 462should be made to re-check this file system. 463If another allocated inode with a zero link count is found, 464this error condition is repeated. 465.IP NO 466terminate the program. 467.sp 468.LP 469.B "\fIB\fP BAD I=\fII\fP" --- 18 unchanged lines hidden (view full) --- 488the number of last block in the file system associated with inode \fII\fP. 489.LP 490Possible responses to the CONTINUE prompt are: 491.IP YES 492ignore the rest of the blocks in this inode 493and continue checking with the next inode in the file system. 494This error condition will not allow a complete check of the file system. 495A second run of | 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" --- 18 unchanged lines hidden (view full) --- 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 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 |
| 496.I fsck | 497.I fsck_ffs |
| 497should be made to re-check this file system. 498.IP NO 499terminate the program. 500.sp 501.LP 502.B "BAD STATE DDD TO BLKERR" 503.br 504An internal error has scrambled | 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 |
| 505.I fsck 's | 506.I fsck_ffs 's |
| 506state map to have the impossible value \fIDDD\fP. | 507state map to have the impossible value \fIDDD\fP. |
| 507.I Fsck | 508.I Fsck_ffs |
| 508exits immediately. 509See a guru. 510.sp 511.LP 512.B "\fIB\fP DUP I=\fII\fP" 513.br 514Inode \fII\fP contains block number \fIB\fP that is already claimed by 515another inode. --- 12 unchanged lines hidden (view full) --- 528inodes. 529.LP 530Possible responses to the CONTINUE prompt are: 531.IP YES 532ignore the rest of the blocks in this inode 533and continue checking with the next inode in the file system. 534This error condition will not allow a complete check of the file system. 535A second run of | 509exits immediately. 510See a guru. 511.sp 512.LP 513.B "\fIB\fP DUP I=\fII\fP" 514.br 515Inode \fII\fP contains block number \fIB\fP that is already claimed by 516another inode. --- 12 unchanged lines hidden (view full) --- 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 file system. 535This error condition will not allow a complete check of the file system. 536A second run of |
| 536.I fsck | 537.I fsck_ffs |
| 537should be made to re-check this file system. 538.IP NO 539terminate the program. 540.sp 541.LP 542.B "DUP TABLE OVERFLOW (CONTINUE)" 543.br 544An internal table in | 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 |
| 545.I fsck | 546.I fsck_ffs |
| 546containing duplicate block numbers cannot allocate any more space. 547Increase the amount of virtual memory available to | 547containing duplicate block numbers cannot allocate any more space. 548Increase the amount of virtual memory available to |
| 548.I fsck . | 549.I fsck_ffs . |
| 549.LP 550Possible responses to the CONTINUE prompt are: 551.IP YES 552continue with the program. 553This error condition will not allow a complete check of the file system. 554A second run of | 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 file system. 555A second run of |
| 555.I fsck | 556.I fsck_ffs |
| 556should be made to re-check this file system. 557If another duplicate block is found, this error condition will repeat. 558.IP NO 559terminate the program. 560.sp 561.LP 562.B "PARTIALLY ALLOCATED INODE I=\fII\fP (CLEAR)" 563.br --- 58 unchanged lines hidden (view full) --- 622.LP 623Possible responses to the ALLOCATE prompt are: 624.IP YES 625allocate inode 2 as the root inode. 626The files and directories usually found in the root will be recovered 627in Phase 3 and put into 628.I lost+found . 629If the attempt to allocate the root fails, | 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 --- 58 unchanged lines hidden (view full) --- 623.LP 624Possible responses to the ALLOCATE prompt are: 625.IP YES 626allocate inode 2 as the root inode. 627The files and directories usually found in the root will be recovered 628in Phase 3 and put into 629.I lost+found . 630If the attempt to allocate the root fails, |
| 630.I fsck | 631.I fsck_ffs |
| 631will exit with the message: 632.br 633.B "CANNOT ALLOCATE ROOT INODE" . 634.IP NO | 632will exit with the message: 633.br 634.B "CANNOT ALLOCATE ROOT INODE" . 635.IP NO |
| 635.I fsck | 636.I fsck_ffs |
| 636will exit. 637.sp 638.LP 639.B "ROOT INODE NOT DIRECTORY (REALLOCATE)" 640.br 641The root inode (usually inode number 2) 642is not directory inode type. 643.LP 644Possible responses to the REALLOCATE prompt are: 645.IP YES 646clear the existing contents of the root inode 647and reallocate it. 648The files and directories usually found in the root will be recovered 649in Phase 3 and put into 650.I lost+found . 651If the attempt to allocate the root fails, | 637will exit. 638.sp 639.LP 640.B "ROOT INODE NOT DIRECTORY (REALLOCATE)" 641.br 642The root inode (usually inode number 2) 643is not directory inode type. 644.LP 645Possible responses to the REALLOCATE prompt are: 646.IP YES 647clear the existing contents of the root inode 648and reallocate it. 649The files and directories usually found in the root will be recovered 650in Phase 3 and put into 651.I lost+found . 652If the attempt to allocate the root fails, |
| 652.I fsck | 653.I fsck_ffs |
| 653will exit with the message: 654.br 655.B "CANNOT ALLOCATE ROOT INODE" . 656.IP NO | 654will exit with the message: 655.br 656.B "CANNOT ALLOCATE ROOT INODE" . 657.IP NO |
| 657.I fsck | 658.I fsck_ffs |
| 658will then prompt with 659.B "FIX" 660.LP 661Possible responses to the FIX prompt are: 662.IP YES 663replace the root inode's type to be a directory. 664If the root inode's data blocks are not directory blocks, 665many error conditions will be produced. --- 9 unchanged lines hidden (view full) --- 675Possible responses to the REALLOCATE prompt are: 676.IP YES 677clear the existing contents of the root inode 678and reallocate it. 679The files and directories usually found in the root will be recovered 680in Phase 3 and put into 681.I lost+found . 682If the attempt to allocate the root fails, | 659will then prompt with 660.B "FIX" 661.LP 662Possible responses to the FIX prompt are: 663.IP YES 664replace the root inode's type to be a directory. 665If the root inode's data blocks are not directory blocks, 666many error conditions will be produced. --- 9 unchanged lines hidden (view full) --- 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 . 683If the attempt to allocate the root fails, |
| 683.I fsck | 684.I fsck_ffs |
| 684will exit with the message: 685.br 686.B "CANNOT ALLOCATE ROOT INODE" . 687.IP NO | 685will exit with the message: 686.br 687.B "CANNOT ALLOCATE ROOT INODE" . 688.IP NO |
| 688.I fsck | 689.I fsck_ffs |
| 689will then prompt with 690.B "CONTINUE" . 691.LP 692Possible responses to the CONTINUE prompt are: 693.IP YES 694ignore the 695.B "DUPS/BAD" 696error condition in the root inode and --- 132 unchanged lines hidden (view full) --- 829leave the directory unchanged. 830.sp 831.LP 832.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" 833.br 834.B "CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS \fIF\fP" 835.br 836A directory \fII\fP has been found whose first entry is \fIF\fP. | 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 --- 132 unchanged lines hidden (view full) --- 830leave the directory unchanged. 831.sp 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. |
| 837.I Fsck | 838.I Fsck_ffs |
| 838cannot resolve this problem. 839The file system should be mounted and the offending entry \fIF\fP 840moved elsewhere. 841The file system should then be unmounted and | 839cannot resolve this problem. 840The file system should be mounted and the offending entry \fIF\fP 841moved elsewhere. 842The file system should then be unmounted and |
| 842.I fsck | 843.I fsck_ffs |
| 843should be run again. 844.sp 845.LP 846.B "MISSING `.' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" 847.br 848.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `.'" 849.br 850A directory \fII\fP has been found whose first entry is not `.'. | 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 851A directory \fII\fP has been found whose first entry is not `.'. |
| 851.I Fsck | 852.I Fsck_ffs |
| 852cannot resolve this problem as it should never happen. 853See a guru. 854.sp 855.LP 856.B "EXTRA `.' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" 857.br 858A directory \fII\fP has been found that has more than one entry for `.'. 859.LP --- 29 unchanged lines hidden (view full) --- 889leave the directory unchanged. 890.sp 891.LP 892.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" 893.br 894.B "CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS \fIF\fP" 895.br 896A directory \fII\fP has been found whose second entry is \fIF\fP. | 853cannot resolve this problem as it should never happen. 854See a guru. 855.sp 856.LP 857.B "EXTRA `.' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" 858.br 859A directory \fII\fP has been found that has more than one entry for `.'. 860.LP --- 29 unchanged lines hidden (view full) --- 890leave the directory unchanged. 891.sp 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. |
| 897.I Fsck | 898.I Fsck_ffs |
| 898cannot resolve this problem. 899The file system should be mounted and the offending entry \fIF\fP 900moved elsewhere. 901The file system should then be unmounted and | 899cannot resolve this problem. 900The file system should be mounted and the offending entry \fIF\fP 901moved elsewhere. 902The file system should then be unmounted and |
| 902.I fsck | 903.I fsck_ffs |
| 903should be run again. 904.sp 905.LP 906.B "MISSING `..' I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP" 907.br 908.B "CANNOT FIX, INSUFFICIENT SPACE TO ADD `..'" 909.br 910A directory \fII\fP has been found whose second entry is not `..'. | 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 `..'. |
| 911.I Fsck | 912.I Fsck_ffs |
| 912cannot resolve this problem. 913The file system should be mounted and the second entry in the directory 914moved elsewhere. 915The file system should then be unmounted and | 913cannot resolve this problem. 914The file system should be mounted and the second entry in the directory 915moved elsewhere. 916The file system should then be unmounted and |
| 916.I fsck | 917.I fsck_ffs |
| 917should be run again. 918.sp 919.LP 920.B "EXTRA `..' ENTRY I=\fII\fP OWNER=\fIO\fP MODE=\fIM\fP SIZE=\fIS\fP MTIME=\fIT\fP DIR=\fIF\fP (FIX)" 921.br 922A directory \fII\fP has been found that has more than one entry for `..'. 923.LP 924Possible responses to the FIX prompt are: 925.IP YES 926remove the extra entry for `..'. 927.IP NO 928leave the directory unchanged. 929.sp 930.LP 931.B "\fIN\fP IS AN EXTRANEOUS HARD LINK TO A DIRECTORY \fID\fP (REMOVE) 932.br | 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 925Possible responses to the FIX prompt are: 926.IP YES 927remove the extra entry for `..'. 928.IP NO 929leave the directory unchanged. 930.sp 931.LP 932.B "\fIN\fP IS AN EXTRANEOUS HARD LINK TO A DIRECTORY \fID\fP (REMOVE) 933.br |
| 933.I Fsck | 934.I Fsck_ffs |
| 934has found a hard link, \fIN\fP, to a directory, \fID\fP. 935When preen'ing the extraneous links are ignored. 936.LP 937Possible responses to the REMOVE prompt are: 938.IP YES 939delete the extraneous entry, \fIN\fP. 940.IP NO 941ignore the error condition. 942.sp 943.LP 944.B "BAD INODE \fIS\fP TO DESCEND" 945.br 946An internal error has caused an impossible state \fIS\fP to be passed to the 947routine that descends the file system directory structure. | 935has found a hard link, \fIN\fP, to a directory, \fID\fP. 936When preen'ing the extraneous links are ignored. 937.LP 938Possible responses to the REMOVE prompt are: 939.IP YES 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 file system directory structure. |
| 948.I Fsck | 949.I Fsck_ffs |
| 949exits. 950See a guru. 951.sp 952.LP 953.B "BAD RETURN STATE \fIS\fP FROM DESCEND" 954.br 955An internal error has caused an impossible state \fIS\fP to be returned 956from the routine that descends the file system directory structure. | 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 file system directory structure. |
| 957.I Fsck | 958.I Fsck_ffs |
| 958exits. 959See a guru. 960.sp 961.LP 962.B "BAD STATE \fIS\fP FOR ROOT INODE" 963.br 964An internal error has caused an impossible state \fIS\fP to be assigned 965to the root inode. | 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 966to the root inode. |
| 966.I Fsck | 967.I Fsck_ffs |
| 967exits. 968See a guru. 969.NH 2 970Phase 3 \- Check Connectivity 971.PP 972This phase concerns itself with the directory connectivity seen in 973Phase 2. 974This section lists error conditions resulting from --- 28 unchanged lines hidden (view full) --- 1003.sp 1004.LP 1005.B "NO lost+found DIRECTORY (CREATE)" 1006.br 1007There is no 1008.I lost+found 1009directory in the root directory of the file system; 1010When preen'ing | 968exits. 969See a guru. 970.NH 2 971Phase 3 \- Check Connectivity 972.PP 973This phase concerns itself with the directory connectivity seen in 974Phase 2. 975This section lists error conditions resulting from --- 28 unchanged lines hidden (view full) --- 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 file system; 1011When preen'ing |
| 1011.I fsck | 1012.I fsck_ffs |
| 1012tries to create a \fIlost+found\fP directory. 1013.LP 1014Possible responses to the CREATE prompt are: 1015.IP YES 1016create a \fIlost+found\fP directory in the root of the file system. 1017This may raise the message: 1018.br 1019.B "NO SPACE LEFT IN / (EXPAND)" --- 44 unchanged lines hidden (view full) --- 1064directory is expanded. 1065.LP 1066Possible responses to the EXPAND prompt are: 1067.IP YES 1068the 1069.I lost+found 1070directory is expanded to make room for the new entry. 1071If the attempted expansion fails | 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 file system. 1018This may raise the message: 1019.br 1020.B "NO SPACE LEFT IN / (EXPAND)" --- 44 unchanged lines hidden (view full) --- 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 |
| 1072.I fsck | 1073.I fsck_ffs |
| 1073prints the message: 1074.br 1075.B "SORRY. NO SPACE IN lost+found DIRECTORY" 1076.br 1077and aborts the attempt to linkup the lost inode. 1078This will always invoke the UNREF error condition in Phase 4. 1079Clean out unnecessary entries in 1080.I lost+found . --- 30 unchanged lines hidden (view full) --- 1111.IP NO 1112ignore the error condition. 1113.sp 1114.LP 1115.B "BAD INODE \fIS\fP TO DESCEND" 1116.br 1117An internal error has caused an impossible state \fIS\fP to be passed to the 1118routine that descends the file system directory structure. | 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 . --- 30 unchanged lines hidden (view full) --- 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 file system directory structure. |
| 1119.I Fsck | 1120.I Fsck_ffs |
| 1120exits. 1121See a guru. 1122.NH 2 1123Phase 4 \- Check Reference Counts 1124.PP 1125This phase concerns itself with the link count information 1126seen in Phase 2 and Phase 3. 1127This section lists error conditions resulting from --- 47 unchanged lines hidden (view full) --- 1175.sp 1176.LP 1177.B "NO lost+found DIRECTORY (CREATE)" 1178.br 1179There is no 1180.I lost+found 1181directory in the root directory of the file system; 1182When preen'ing | 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 --- 47 unchanged lines hidden (view full) --- 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 file system; 1183When preen'ing |
| 1183.I fsck | 1184.I fsck_ffs |
| 1184tries to create a \fIlost+found\fP directory. 1185.LP 1186Possible responses to the CREATE prompt are: 1187.IP YES 1188create a \fIlost+found\fP directory in the root of the file system. 1189This may raise the message: 1190.br 1191.B "NO SPACE LEFT IN / (EXPAND)" --- 44 unchanged lines hidden (view full) --- 1236directory is expanded. 1237.LP 1238Possible responses to the EXPAND prompt are: 1239.IP YES 1240the 1241.I lost+found 1242directory is expanded to make room for the new entry. 1243If the attempted expansion fails | 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 file system. 1190This may raise the message: 1191.br 1192.B "NO SPACE LEFT IN / (EXPAND)" --- 44 unchanged lines hidden (view full) --- 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 |
| 1244.I fsck | 1245.I fsck_ffs |
| 1245prints the message: 1246.br 1247.B "SORRY. NO SPACE IN lost+found DIRECTORY" 1248.br 1249and aborts the attempt to linkup the lost inode. 1250This will always invoke the UNREF error condition in Phase 4. 1251Clean out unnecessary entries in 1252.I lost+found . --- 8 unchanged lines hidden (view full) --- 1261The link count for inode \fII\fP, 1262is \fIX\fP but should be \fIY\fP. 1263The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP 1264are printed. 1265When preen'ing the link count is adjusted unless the number of references 1266is increasing, a condition that should never occur unless precipitated 1267by a hardware failure. 1268When the number of references is increasing under preen mode, | 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 . --- 8 unchanged lines hidden (view full) --- 1262The link count for inode \fII\fP, 1263is \fIX\fP but should be \fIY\fP. 1264The owner \fIO\fP, mode \fIM\fP, size \fIS\fP, and modify time \fIT\fP 1265are printed. 1266When preen'ing the link count is adjusted unless the number of references 1267is increasing, a condition that should never occur unless precipitated 1268by a hardware failure. 1269When the number of references is increasing under preen mode, |
| 1269.I fsck | 1270.I fsck_ffs |
| 1270exits with the message: 1271.br 1272.B "LINK COUNT INCREASING" 1273.LP 1274Possible responses to the ADJUST prompt are: 1275.IP YES 1276replace the link count of file inode \fII\fP with \fIY\fP. 1277.IP NO --- 113 unchanged lines hidden (view full) --- 1391\fIY\fP free fragments and 1392\fIZ\fP free full sized blocks. 1393.sp 1394.LP 1395.B "***** REBOOT UNIX *****" 1396.br 1397This is an advisory message indicating that 1398the root file system has been modified by | 1271exits with the message: 1272.br 1273.B "LINK COUNT INCREASING" 1274.LP 1275Possible responses to the ADJUST prompt are: 1276.IP YES 1277replace the link count of file inode \fII\fP with \fIY\fP. 1278.IP NO --- 113 unchanged lines hidden (view full) --- 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 file system has been modified by |
| 1399.I fsck. | 1400.I fsck_ffs. |
| 1400If UNIX is not rebooted immediately, 1401the work done by | 1401If UNIX is not rebooted immediately, 1402the work done by |
| 1402.I fsck | 1403.I fsck_ffs |
| 1403may be undone by the in-core copies of tables 1404UNIX keeps. 1405When preen'ing, | 1404may be undone by the in-core copies of tables 1405UNIX keeps. 1406When preen'ing, |
| 1406.I fsck | 1407.I fsck_ffs |
| 1407will exit with a code of 4. 1408The standard auto-reboot script distributed with 4.3BSD 1409interprets an exit code of 4 by issuing a reboot system call. 1410.sp 1411.LP 1412.B "***** FILE SYSTEM WAS MODIFIED *****" 1413.br 1414This is an advisory message indicating that 1415the current file system was modified by | 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 file system was modified by |
| 1416.I fsck. | 1417.I fsck_ffs. |
| 1417If this file system is mounted or is the current root file system, | 1418If this file system is mounted or is the current root file system, |
| 1418.I fsck | 1419.I fsck_ffs |
| 1419should be halted and UNIX rebooted. 1420If UNIX is not rebooted immediately, 1421the work done by | 1420should be halted and UNIX rebooted. 1421If UNIX is not rebooted immediately, 1422the work done by |
| 1422.I fsck | 1423.I fsck_ffs |
| 1423may be undone by the in-core copies of tables 1424UNIX keeps. | 1424may be undone by the in-core copies of tables 1425UNIX keeps. |