From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 23:24:58 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 A234716A4CE for ; Thu, 4 Mar 2004 23:24:58 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id E20D643D2F for ; Thu, 4 Mar 2004 23:24:32 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 4260 invoked from network); 5 Mar 2004 07:22:33 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 5 Mar 2004 07:22:33 -0000 Received: from it.buh.cameradicommercio.ro (localhost.buh.cameradicommercio.ro [127.0.0.1]) by it.buh.cameradicommercio.ro (Postfix) with SMTP id 52A101C5; Fri, 5 Mar 2004 09:24:32 +0200 (EET) Date: Fri, 5 Mar 2004 09:24:31 +0200 From: Ion-Mihai Tetcu To: Tim Robbins Message-Id: <20040305092431.2279d5c1@it.buh.cameradicommercio.ro> In-Reply-To: <20040305070851.GA72131@cat.robbins.dropbear.id.au> References: <20040305070851.GA72131@cat.robbins.dropbear.id.au> X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: "'current@freebsd.org'" Subject: Re: 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, 05 Mar 2004 07:24:58 -0000 On Fri, 5 Mar 2004 18:08:51 +1100 Tim Robbins wrote: > On Fri, Mar 05, 2004 at 12:31:51AM -0500, Don Bowman wrote: > > > periodically (once a day or so), i'm getting a panic > > as 'panic: ffs_blkfree: freeing free block'. > [...] > > Suggestions on what I should look for or try? > > Dropping to single user mode & forcing a fsck (with the -f option) > should fix this. It's a symptom of some kind of filesystem > inconsistency that soft updates isn't expecting, and that background > fsck isn't trying to detect or repair. I would first try to do a fsck -n. If you get a lot of this bad block -1428886735890689256, ino 2049427 DON'T fsck unless you have back-ups (in which case newfs would be easier and less time consuming). Otherwise try to copy the data out of it provided you can mount the disk (which you probably can.) Experience speaking (on ATA, not SCSI): fsck dumping core on this errors, or in the god case "recovering" next to zero, but Gigs of files in good state (read correct md5 sums); reproduce a few times. Strange, at lest to me. In any case investigate the hardware. -- IOnut Unregistered ;) FreeBSD user