| 1.t (1558) | 1.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/1.t 66861 2000-10-09 08:26:35Z adrian $ |
|
| 32.\" @(#)1.t 8.1 (Berkeley) 6/5/93 33.\" 34.ds RH Introduction 35.NH 36Introduction 37.PP 38This document reflects the use of | 33.\" @(#)1.t 8.1 (Berkeley) 6/5/93 34.\" 35.ds RH Introduction 36.NH 37Introduction 38.PP 39This document reflects the use of |
| 39.I fsck | 40.I fsck_ffs |
| 40with the 4.2BSD and 4.3BSD file system organization. This 41is a revision of the 42original paper written by 43T. J. Kowalski. 44.PP 45When a UNIX 46operating system is brought up, a consistency 47check of the file systems should always be performed. 48This precautionary measure helps to insure 49a reliable environment for file storage on disk. 50If an inconsistency is discovered, 51corrective action must be taken. | 41with the 4.2BSD and 4.3BSD file system organization. This 42is a revision of the 43original paper written by 44T. J. Kowalski. 45.PP 46When a UNIX 47operating system is brought up, a consistency 48check of the file systems should always be performed. 49This precautionary measure helps to insure 50a reliable environment for file storage on disk. 51If an inconsistency is discovered, 52corrective action must be taken. |
| 52.I Fsck | 53.I Fsck_ffs |
| 53runs in two modes. 54Normally it is run non-interactively by the system after 55a normal boot. 56When running in this mode, 57it will only make changes to the file system that are known 58to always be correct. 59If an unexpected inconsistency is found | 54runs in two modes. 55Normally it is run non-interactively by the system after 56a normal boot. 57When running in this mode, 58it will only make changes to the file system that are known 59to always be correct. 60If an unexpected inconsistency is found |
| 60.I fsck | 61.I fsck_ffs |
| 61will exit with a non-zero exit status, 62leaving the system running single-user. 63Typically the operator then runs | 62will exit with a non-zero exit status, 63leaving the system running single-user. 64Typically the operator then runs |
| 64.I fsck | 65.I fsck_ffs |
| 65interactively. 66When running in this mode, 67each problem is listed followed by a suggested corrective action. 68The operator must decide whether or not the suggested correction 69should be made. 70.PP 71The purpose of this memo is to dispel the 72mystique surrounding 73file system inconsistencies. 74It first describes the updating of the file system 75(the calm before the storm) and 76then describes file system corruption (the storm). 77Finally, 78the set of deterministic corrective actions 79used by | 66interactively. 67When running in this mode, 68each problem is listed followed by a suggested corrective action. 69The operator must decide whether or not the suggested correction 70should be made. 71.PP 72The purpose of this memo is to dispel the 73mystique surrounding 74file system inconsistencies. 75It first describes the updating of the file system 76(the calm before the storm) and 77then describes file system corruption (the storm). 78Finally, 79the set of deterministic corrective actions 80used by |
| 80.I fsck | 81.I fsck_ffs |
| 81(the Coast Guard 82to the rescue) is presented. 83.ds RH Overview of the File System | 82(the Coast Guard 83to the rescue) is presented. 84.ds RH Overview of the File System |