From owner-freebsd-current@FreeBSD.ORG Wed Jan 28 09:42:34 2004 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 2EC5416A4CE for ; Wed, 28 Jan 2004 09:42:34 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C73843D39 for ; Wed, 28 Jan 2004 09:42:33 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3E80072DBF; Wed, 28 Jan 2004 09:42:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3BD8B72DB5; Wed, 28 Jan 2004 09:42:33 -0800 (PST) Date: Wed, 28 Jan 2004 09:42:33 -0800 (PST) From: Doug White To: =?iso-8859-1?Q? Georg-W=2E_Koltermann ?= In-Reply-To: <27942123$10752415724016e264dfa7c0.73399806@config8.schlund.de> Message-ID: <20040128094120.T24842@carver.gumbysoft.com> References: <27942123$10752415724016e264dfa7c0.73399806@config8.schlund.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Re: panic: handle_written_inodeblock: live inodedep 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, 28 Jan 2004 17:42:34 -0000 On Tue, 27 Jan 2004 gwk@rahn-koltermann.de wrote: > > Doug White schrieb am 27.01.2004, 20:06:09: > > On Tue, 27 Jan 2004, Georg-W. Koltermann wrote: > > > > > With RELENG_5_2 cvsupped shortly after -RC2, today I got a panic after > > > reboot from a crash, while background fsck was running: > > > > This was fixed in -current recently. > > > > Any info on MFC to RELENG_5_2, or could you point me to the commit that > fixed it? Or should I disable BG fsck in 5.2? Grr, I can't find it right now, but I doubt anything is going into 5.2 while they prep for 5.2.1. Disabling bgfsck is the workaround for now. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org