From owner-freebsd-questions@FreeBSD.ORG Wed Aug 13 11:18:46 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 7195537B401 for ; Wed, 13 Aug 2003 11:18:46 -0700 (PDT) Received: from webserver.get-linux.org (adsl-64-161-78-226.dsl.lsan03.pacbell.net [64.161.78.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 736A343FCB for ; Wed, 13 Aug 2003 11:18:45 -0700 (PDT) (envelope-from oremanj@webserver.get-linux.org) Received: (qmail 3163 invoked by uid 1000); 13 Aug 2003 18:20:12 -0000 Date: Wed, 13 Aug 2003 11:20:12 -0700 From: Joshua Oreman To: Andy Farkas Message-ID: <20030813182012.GA3027@webserver> References: <20030813043621.GA560@webserver> <20030813144131.C90272-100000@hewey.af.speednet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030813144131.C90272-100000@hewey.af.speednet.com.au> User-Agent: Mutt/1.4.1i cc: questions@freebsd.org Subject: Re: fsck -F 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: Wed, 13 Aug 2003 18:18:46 -0000 On Wed, Aug 13, 2003 at 02:51:00PM +1000 or thereabouts, Andy Farkas wrote: > Joshua Oreman wrote: > > > > fsck already runs at boot. > > > > Yes. But they won't run if the filesystem is marked ``clean''. > > Why would you want to fsck a clean disk? During every boot??? > > > Actually, what shutdown -F does is touch /forcefsck. (In a similar vein, > > shutdown -f touches /fastboot). The rc scripts check this and add appropriate > > flags to the invocation of fsck (or in the case of /fastboot don't invoke it). > > You must be talking about another OS. FreeBSD's shutdown doesnt have -F or -f flag. I was giving the example in Linux that the OP asked about, so they could implement it under FBSD if they wanted. I said that in my mail, in the part you trimmed. One would check for the existence of /forcefsck in the rc scripts and, if it was there, run fsck *for that one boot* even if the filesystems were clean. Then /forcefsck would be removed so it didn't happen on the next boot. Shutdown *could* be patched to add an option for this if it was implemented in the rc scripts. Why one would want to do this, I don't know. But this was what the OP asked. -- Josh > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > >