From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 28 14:48:47 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31F7B1065703 for ; Mon, 28 Jul 2008 14:48:47 +0000 (UTC) (envelope-from fbsd06+YI=b4248589@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id EE05C8FC16 for ; Mon, 28 Jul 2008 14:48:46 +0000 (UTC) (envelope-from fbsd06+YI=b4248589@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by fallback-in1.mxes.net (Postfix) with ESMTP id C1641164204 for ; Mon, 28 Jul 2008 10:32:10 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 25B3023E4B6 for ; Mon, 28 Jul 2008 10:32:08 -0400 (EDT) Date: Mon, 28 Jul 2008 15:32:04 +0100 From: RW To: freebsd-hackers@freebsd.org Message-ID: <20080728153204.567bb54c@gumby.homeunix.com.> In-Reply-To: <200807281510.12070.marc.loerner@hob.de> References: <488DB785.3020805@gmail.com> <20080728130057.GA798@eos.sc1.parodius.com> <200807281510.12070.marc.loerner@hob.de> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: forcefsck on booting stage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2008 14:48:47 -0000 On Mon, 28 Jul 2008 15:10:11 +0200 Marc L__rner wrote: > On Monday 28 July 2008 15:00, Jeremy Chadwick wrote: > > On Mon, Jul 28, 2008 at 04:11:49PM +0400, sam wrote: > > > Hello, > > > > > > How to make 'fsck -f' on booting stage of remote system? > > > > I believe by setting background_fsck="no" in /etc/rc.conf? That's > > the only way I know of, besides booting single user and doing it > > manually. > > Doesn't this only disable background fsck support? > By creating file "/forcefsck" you can force an fsck at next reboot, > because some scripts test for existence. That's in linux AFAIK, but it would be fairly straightforward to modify /etc/rc.d/fsck to get that behaviour though. fsck -f is interactive, so you would want to add the -y option to prevent its hanging waiting for console input.