From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 15:47:29 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 B880D16A4CE; Wed, 31 Dec 2003 15:47:29 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id A67A943D31; Wed, 31 Dec 2003 15:47:28 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 2BFBE30742; Wed, 31 Dec 2003 18:47:28 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id C513F1D1DC5; Wed, 31 Dec 2003 18:47:30 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16371.24594.660308.151100@canoe.dclg.ca> Date: Wed, 31 Dec 2003 18:47:30 -0500 To: kientzle@acm.org In-Reply-To: <3FF35F60.1070803@acm.org> 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> <3FF35F60.1070803@acm.org> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid 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 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:47:29 -0000 >>>>> "Tim" == Tim Kientzle writes: Tim> The first time fsck gets invoked by rcNG, it is given the -F flag Tim> which, according to fsck(8) does a foreground check on "all the Tim> file systems that cannot do background checking." Tim> I think that "system rebooted during a bg fsck" could qualify Tim> that FS as being unable to do background checking. What's needed Tim> is some way for fsck to mark a filesystem as having a bgfsck in Tim> progress. Then fsck -F can check for that marker. Hrm. Isn't this done? Isn't there a 'special' snapshot created by the bgfsck process? Or does this snapshot evaporate (have no links)? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================