From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 15:44:42 2003 Return-Path: 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 0B3E316A4CE; Wed, 31 Dec 2003 15:44:42 -0800 (PST) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCC8743D31; Wed, 31 Dec 2003 15:44:40 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org ([66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id hBVNiWkX015937; Wed, 31 Dec 2003 15:44:33 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3FF35F60.1070803@acm.org> Date: Wed, 31 Dec 2003 15:44:32 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Barton References: <20031229164130.GA797@pp.htv.fi> <16370.20382.81302.449649@canoe.dclg.ca> <16371.20373.212950.533985@canoe.dclg.ca> <20031231152453.G1441@bo.vpnaa.bet> In-Reply-To: <20031231152453.G1441@bo.vpnaa.bet> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Esa Karkkainen cc: "current@freebsd.org" cc: David Gilbert Subject: Re: 5.1-R-p11 unable to "sync disks" when shutting down X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2003 23:44:42 -0000 Doug Barton wrote: > On Wed, 31 Dec 2003, David Gilbert wrote: >>I'd like to see: >> >>crash -> boot -> defer for bgfsck (but mark disk as having tried) >> -> multiuser -> bgfsck -> crash -> boot -> fsck in foreground >> -> multiuser >> >>... but I believe this would require fsck support unless the startup >>scripts were writing to the filesystem to indicate no bgfsck. > > > What you propose would also be really complicated for other reasons > related to the way rcNG works. I agree that it would be tricky to handle within the startup scripts. But it doesn't seem like it should be hard to handle within fsck itself. The first time fsck gets invoked by rcNG, it is given the -F flag which, according to fsck(8) does a foreground check on "all the file systems that cannot do background checking." I think that "system rebooted during a bg fsck" could qualify that FS as being unable to do background checking. What's needed is some way for fsck to mark a filesystem as having a bgfsck in progress. Then fsck -F can check for that marker. Tim