From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 15:55:55 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 C16DB37B401 for ; Fri, 27 Jun 2003 15:55:55 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED85043FBD for ; Fri, 27 Jun 2003 15:55:54 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id QAA20687 for ; Fri, 27 Jun 2003 16:55:50 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030627165224.03568100@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 27 Jun 2003 16:55:45 -0600 To: questions@freebsd.org From: Brett Glass Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: 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 22:55:56 -0000 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? --Brett Glass