From owner-freebsd-questions@FreeBSD.ORG Sat Jun 28 10:18:06 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 BBA7E37B401 for ; Sat, 28 Jun 2003 10:18:06 -0700 (PDT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA5334400B for ; Sat, 28 Jun 2003 10:18:05 -0700 (PDT) (envelope-from cswiger@mac.com) Received: from mac.com ([141.149.47.46]) by out001.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030628171805.XHJR12592.out001.verizon.net@mac.com>; Sat, 28 Jun 2003 12:18:05 -0500 Message-ID: <3EFDCDCC.7010507@mac.com> Date: Sat, 28 Jun 2003 13:18:04 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Glass References: <4.3.2.7.2.20030627165224.03568100@localhost> <4.3.2.7.2.20030627165224.03568100@localhost> <4.3.2.7.2.20030627195013.029d4a70@localhost> In-Reply-To: <4.3.2.7.2.20030627195013.029d4a70@localhost> X-Enigmail-Version: 0.76.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.149.47.46] at Sat, 28 Jun 2003 12:18:04 -0500 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 17:18:07 -0000 Brett Glass wrote: [ ... ] > 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.) Unattended restarts can more difficult, agreed. > 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. Most of the time-- and by that I mean more than 90% of the time-- the system is capable of fsck'ing itself automatically and without the need for human intervention. This is more true for relatively quiet or read-only systems, and less true for systems which are very busy, have many writes pending, etc. You might want to consider using a journalling filesystem instead, although you would have to switch platforms and pay for something like Veritas VxFS. > 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.) The following option for /etc/rc.conf may be of interest to you: #fsck_y_enable='YES' ...it's not as safe as the default preen, but if your concern is to have the system "handle the logistics" without human intervention if at all possible, this might be want you want. -- -Chuck