From owner-freebsd-current@FreeBSD.ORG Tue Feb 19 14:13:50 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F79616A473 for ; Tue, 19 Feb 2008 14:13:50 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 19C6213C4D1 for ; Tue, 19 Feb 2008 14:13:49 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id AA18619E071 for ; Tue, 19 Feb 2008 15:13:48 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTP id 95D9B19E054 for ; Tue, 19 Feb 2008 15:13:46 +0100 (CET) Message-ID: <47BAE428.1040101@quip.cz> Date: Tue, 19 Feb 2008 15:14:00 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, cs, en, en-us MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG References: <200802191349.m1JDnhp9029723@lurza.secnetix.de> In-Reply-To: <200802191349.m1JDnhp9029723@lurza.secnetix.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: panic: ffs_blkfree: freeing free block (7.0-RC1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 19 Feb 2008 14:13:50 -0000 Oliver Fromme wrote: > Miroslav Lachman wrote: > > panic: ffs_blkfree: freeing free block > > I had exactly the same panic, also on a FreeBSD 7 system > with gmirror. I'm not sure if it's related, but I tell > you my story anyway ... > > Apparently it was caused by a bug that caused corruption > in the file system. The bug was fixed in October, IIRC, > but the corruption remained and eventually crashed the > machine again. A forced fsck ("fsck -f -y") seems to have > fixed it for me finally. > > So, my recommendation is this: > - Make sure you update to the latest sources. > - "fsck -f -y" all your filesystems in single-user mode. > Alternatively, newfs them and restore from backup. This was on 1 week old (brand new HW) machine. Just installed and put it in production (migration from one datacenter to another) so I think that it is not affected by anything from October or before. /vol0 and /vol1 was newfs-ed about 2 days befor kernel panic. But thank you for suggesion anyway. Miroslav Lachman