From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 00:35:02 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14E751065676 for ; Tue, 13 Jan 2009 00:35:02 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id CC3708FC16 for ; Tue, 13 Jan 2009 00:35:01 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id E7B7817E56; Tue, 13 Jan 2009 11:35:02 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-13-120.lns10.syd7.internode.on.net [121.44.13.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id EE61D17429; Tue, 13 Jan 2009 11:34:58 +1100 (EST) Message-ID: <496BE193.4070807@modulus.org> Date: Tue, 13 Jan 2009 11:34:27 +1100 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Andriy Gapon References: <496B3E28.3070902@icyb.net.ua> In-Reply-To: <496B3E28.3070902@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: fsck_y_enable: suboptimal/odd? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 00:35:02 -0000 Andriy Gapon wrote: > To me it seems like fsck_y passes suboptimal flags to fsck, it doesn't > have to examine each and every filesystem in fstab. I think think this is because it does a quick check first to see if it can run the fsck in background after boot into multi-user mode. If it cannot, then fsck exits and is re-run with fsck -y and runs in foreground mode. - Andrew