From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 28 13:09:07 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 BEF51106564A for ; Mon, 28 Jul 2008 13:09:07 +0000 (UTC) (envelope-from marc.loerner@hob.de) Received: from mailgate.hob.de (mailgate.hob.de [212.185.199.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7A7338FC14 for ; Mon, 28 Jul 2008 13:09:07 +0000 (UTC) (envelope-from marc.loerner@hob.de) Received: from imap.hob.de (mail2.hob.de [172.25.1.102]) by mailgate.hob.de (Postfix) with ESMTP id D81BE52009B for ; Mon, 28 Jul 2008 15:09:05 +0200 (CEST) Received: from linux03.hob.de (linux03.hob.de [172.22.0.190]) by imap.hob.de (Postfix on SuSE eMail Server 2.0) with ESMTP id 82A7DFD557 for ; Mon, 28 Jul 2008 15:09:05 +0200 (CEST) From: Marc =?iso-8859-1?q?L=F6rner?= Organization: hob To: freebsd-hackers@freebsd.org Date: Mon, 28 Jul 2008 15:10:11 +0200 User-Agent: KMail/1.6.2 References: <488DB785.3020805@gmail.com> <20080728130057.GA798@eos.sc1.parodius.com> In-Reply-To: <20080728130057.GA798@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200807281510.12070.marc.loerner@hob.de> 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 13:09:07 -0000 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. HTH, Marc Loerner