From owner-freebsd-current@FreeBSD.ORG Fri May 2 04:59:49 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 4F65637B401 for ; Fri, 2 May 2003 04:59:49 -0700 (PDT) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B47FB43FBF for ; Fri, 2 May 2003 04:59:47 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (210.50.217.185) by smtp02.syd.iprimus.net.au (7.0.012) id 3E8A160000579097; Fri, 2 May 2003 21:59:45 +1000 Received: by dilbert.robbins.dropbear.id.au (Postfix, from userid 1000) id 6C12EC90D; Fri, 2 May 2003 21:59:34 +1000 (EST) Date: Fri, 2 May 2003 21:59:34 +1000 From: Tim Robbins To: David Xu Message-ID: <20030502215934.A82247@dilbert.robbins.dropbear.id.au> References: <20030501135011.GA568@wombat.fafoe><86r87ixlb0.fsf@xa12.heimat.gr.jp> <3EB1BF31.B96B7A3C@mindspring.com> <001901c3109e$7c733cb0$0701a8c0@tiger> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <001901c3109e$7c733cb0$0701a8c0@tiger>; from davidxu@freebsd.org on Fri, May 02, 2003 at 07:32:16PM +0800 cc: freebsd-current@freebsd.org Subject: Re: another panic: ffs_blkfree: freeing free block 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: Fri, 02 May 2003 11:59:49 -0000 On Fri, May 02, 2003 at 07:32:16PM +0800, David Xu wrote: [...] > panic: ffs_blkfree: freeing free block [...] Can you try running fsck on the filesystem in single-user mode instead of letting background fsck do it? I was getting a lot of strange UFS-related panics a few months ago and they went away after I ran fsck. The recent surge of reports of this panic seems to hint at a more recent bug, but I thought I'd just suggest this anyway... Tim