From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 16:11:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9025037B419 for ; Fri, 27 Jun 2003 16:11:02 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF84443FEA for ; Fri, 27 Jun 2003 16:11:01 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h5RNB1p6014478; Fri, 27 Jun 2003 18:11:01 -0500 (CDT) (envelope-from dan) Date: Fri, 27 Jun 2003 18:11:00 -0500 From: Dan Nelson To: Brett Glass Message-ID: <20030627231100.GB1815@dan.emsphone.com> References: <4.3.2.7.2.20030627165224.03568100@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030627165224.03568100@localhost> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: questions@freebsd.org Subject: Re: fsck! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 23:11:05 -0000 In the last episode (Jun 27), Brett Glass said: > Often, after a FreeBSD 4.x system has been powered down without a > proper shutdown, the system complains of inconsistencies on the disk. > Yet, if one runs the command "fsck -f" after it's rebooted, the fsck > program doesn't fix the problems it finds; instead, it says "NO > WRITE" at the beginning of each report. (It seems not to want to > touch things unless they're unmounted.) So, the system has to come > down AGAIN. > > What's the best and fastest way of ensuring disk consistency on a > system that you're powering up after an abrupt outage? What about a > system that powered up again before you arrived to nurse it through a > reboot? An fsck that fails with "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY." should cause the boot process to stop right there and drop to single-user mode. Under 4.x, it will run fsck -p on any dirty filesystems, and only if the preen returned success on all filesystems will it continue to multi-user mode. 5.x is a bit more lenient, since it can clean softupdates filesystems in the background. -- Dan Nelson dnelson@allantgroup.com