Date: Wed, 28 Jan 2004 09:42:33 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: =?iso-8859-1?Q? Georg-W=2E_Koltermann ?= <gwk@rahn-koltermann.de> Cc: freebsd-current@freebsd.org Subject: Re: Re: panic: handle_written_inodeblock: live inodedep Message-ID: <20040128094120.T24842@carver.gumbysoft.com> In-Reply-To: <27942123$10752415724016e264dfa7c0.73399806@config8.schlund.de> References: <27942123$10752415724016e264dfa7c0.73399806@config8.schlund.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Jan 2004 gwk@rahn-koltermann.de wrote: > > Doug White <dwhite@gumbysoft.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040128094120.T24842>