| 1.t (96707) | 1.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/1.t 96707 2002-05-16 04:10:46Z trhodes $ | 32.\" $FreeBSD: head/sbin/fsck_ffs/SMM.doc/1.t 102231 2002-08-21 18:11:48Z trhodes $ |
| 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 40.I fsck_ffs | 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 40.I fsck_ffs |
| 41with the 4.2BSD and 4.3BSD filesystem organization. This | 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 | 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 filesystems should always be performed. | 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. 53.I Fsck_ffs 54runs in two modes. 55Normally it is run non-interactively by the system after 56a normal boot. 57When running in this mode, | 49This precautionary measure helps to insure 50a reliable environment for file storage on disk. 51If an inconsistency is discovered, 52corrective action must be taken. 53.I Fsck_ffs 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 filesystem that are known | 58it will only make changes to the file system that are known |
| 59to always be correct. 60If an unexpected inconsistency is found 61.I fsck_ffs 62will exit with a non-zero exit status, 63leaving the system running single-user. 64Typically the operator then runs 65.I fsck_ffs 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 | 59to always be correct. 60If an unexpected inconsistency is found 61.I fsck_ffs 62will exit with a non-zero exit status, 63leaving the system running single-user. 64Typically the operator then runs 65.I fsck_ffs 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 |
| 74filesystem inconsistencies. 75It first describes the updating of the filesystem | 74file system inconsistencies. 75It first describes the updating of the file system |
| 76(the calm before the storm) and | 76(the calm before the storm) and |
| 77then describes filesystem corruption (the storm). | 77then describes file system corruption (the storm). |
| 78Finally, 79the set of deterministic corrective actions 80used by 81.I fsck_ffs 82(the Coast Guard 83to the rescue) is presented. 84.ds RH Overview of the File System | 78Finally, 79the set of deterministic corrective actions 80used by 81.I fsck_ffs 82(the Coast Guard 83to the rescue) is presented. 84.ds RH Overview of the File System |