From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 14:37:08 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 E61C316A4CE for ; Wed, 31 Dec 2003 14:37:08 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id D46B043D1F for ; Wed, 31 Dec 2003 14:37:07 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 59B6230774; Wed, 31 Dec 2003 17:37:07 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 54BE81D1D54; Wed, 31 Dec 2003 17:37:09 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16371.20373.212950.533985@canoe.dclg.ca> Date: Wed, 31 Dec 2003 17:37:09 -0500 To: Esa Karkkainen In-Reply-To: <20031231073244.GA44710@pp.htv.fi> References: <20031229164130.GA797@pp.htv.fi> <16370.20382.81302.449649@canoe.dclg.ca> <20031231073244.GA44710@pp.htv.fi> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid 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 22:37:09 -0000 >>>>> "Esa" == Esa Karkkainen writes: Esa> No, I don't use snapshots any more. I did use snapshots via Esa> bgfsck, but now I have disabled bgfsck, because for some reason I Esa> got panics which seemed to be related to bgfsck. I think it would be _very_ helpful if bgfsck could be made to only run once. Currently, you can have the following: crash -> boot -> defer for bgfsck -> multiuser -> bgfsck -> crash (loop until manual intervention) ... this happens when bgfsck can't fix something. 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. 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================