From owner-freebsd-questions@FreeBSD.ORG Fri Jun 27 18:55:53 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 625AB37B401 for ; Fri, 27 Jun 2003 18:55:53 -0700 (PDT) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A43404400E for ; Fri, 27 Jun 2003 18:55:52 -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 TAA22068; Fri, 27 Jun 2003 19:55:45 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20030627195013.029d4a70@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 27 Jun 2003 19:55:28 -0600 To: Kris Kennaway From: Brett Glass In-Reply-To: <20030628004346.GB55502@rot13.obsecurity.org> References: <4.3.2.7.2.20030627165224.03568100@localhost> <4.3.2.7.2.20030627165224.03568100@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: Sat, 28 Jun 2003 01:55:53 -0000 At 06:43 PM 6/27/2003, Kris Kennaway wrote: >You're supposed to boot into single-user mode to repair the >filesystems before attempting to bring it up to multiuser state. Ah... but you're not there at the exact moment when the power comes back on. (Maybe it was just a flicker and there was no UPS, or maybe the power company -- like ours -- is so slow to fix outages that the UPS battery was fully drained.) What's more, even if you CAN boot into single user mode and run fsck, it can be frustrating. Sometimes a partition takes two or three passes to clean up. Sometimes fsck randomly refuses to work on one. It's a mess. Ideally, the system would handle the logistics. It's not as if powering down without shutting down is that rare of an occurrence. (It eats holes in any system, and is responsible for gradual "bit rot" in both Windows machines and BSD machines.) --Brett