From owner-freebsd-current@FreeBSD.ORG  Mon May  5 23:33:45 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DA79F37B401
	for <freebsd-current@freebsd.org>;
	Mon,  5 May 2003 23:33:44 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 17DCF43FCB
	for <freebsd-current@freebsd.org>;
	Mon,  5 May 2003 23:33:44 -0700 (PDT)	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h466XhA7050211;
	Tue, 6 May 2003 00:33:43 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 06 May 2003 00:31:14 -0600 (MDT)
Message-Id: <20030506.003114.66177783.imp@bsdimp.com>
To: leafy@leafy.idv.tw
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030506012317.GA610@chihiro.leafy.idv.tw>
References: <20030505.112625.16415226.imp@bsdimp.com>
	<20030506012317.GA610@chihiro.leafy.idv.tw>
X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: Precaution!
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2003 06:33:46 -0000

In message: <20030506012317.GA610@chihiro.leafy.idv.tw>
            leafy <leafy@leafy.idv.tw> writes:
: On Mon, May 05, 2003 at 11:26:25AM -0600, M. Warner Losh wrote:
: > If you booted a kernel from approximately April 15th through May 3th,
: > there were a number of small, but critical, vm bugs.  This can cause
: > file system corruption, and leave silent landmines for later.  It is
: > recommended that if you did boot these kernels, you build a newer
: > kernel, come up in single user and force an fsck on all filesystems.
: > This is to prevent 'false' panics later that are a result of the
: > corruption that might be dormant in them now.
: > 
: > Warner
: Is there a way to mimick rc.early in rcNG so that I can force a 'fsck -y' 
: remotely?

I think that background_fsck to 'no' and fsck_y_enable to 'yes' will
do approximately what you want.

Alternatively, the following script in /etc/rc.d might do the trick.
I just typed it into text editor, and ran rcorder, so you need to test
it before use:

$!/bin/sh

# BEFORE: initdiskless
# KEYWORD: FreeBSD

. /etc/rc.subr

name="force_fsck"
start_cmd="force_fsck_start"
stop_cmd=":"

force_fsck_start()
{
	fsck -y
}

load_rc_config $name
run_rc_command "$1"

Warner