From owner-freebsd-current@FreeBSD.ORG Tue Feb 19 13:49:48 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 3BAF916A421 for ; Tue, 19 Feb 2008 13:49:48 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id A4E4513C46A for ; Tue, 19 Feb 2008 13:49:47 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m1JDnhPc029724; Tue, 19 Feb 2008 14:49:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m1JDnhp9029723; Tue, 19 Feb 2008 14:49:43 +0100 (CET) (envelope-from olli) Date: Tue, 19 Feb 2008 14:49:43 +0100 (CET) Message-Id: <200802191349.m1JDnhp9029723@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, 000.fbsd@quip.cz In-Reply-To: <47BAACD7.5050303@quip.cz> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 19 Feb 2008 14:49:46 +0100 (CET) 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 Reply-To: freebsd-current@FreeBSD.ORG, 000.fbsd@quip.cz 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 13:49:48 -0000 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. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I invented Ctrl-Alt-Delete, but Bill Gates made it famous." -- David Bradley, original IBM PC design team