From owner-freebsd-amd64@FreeBSD.ORG Sun Apr 26 12:47:59 2009 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E474B1065672 for ; Sun, 26 Apr 2009 12:47:59 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from batman.home4u.ch (6to4.home4u.ch [IPv6:2002:d908:d3e2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6F7968FC0A for ; Sun, 26 Apr 2009 12:47:58 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from flashback.wenks.ch (flashback.wenks.ch [IPv6:2002:3e02:55b4:2:20a:95ff:fe8f:6586]) (authenticated bits=0) by batman.home4u.ch (8.14.2/8.14.2) with ESMTP id n3QCllhu077307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Apr 2009 14:47:56 +0200 (CEST) (envelope-from fabian@wenks.ch) Message-ID: <49F457ED.10109@wenks.ch> Date: Sun, 26 Apr 2009 14:47:41 +0200 From: Fabian Wenk User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: Rowan Crowe References: <200904241756.n3OHu0WI071774@www.freebsd.org> In-Reply-To: <200904241756.n3OHu0WI071774@www.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/133977: "panic: ffs_blkfree: freeing free block" after 7.0R->7.1R amd64 src upgrade X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2009 12:48:00 -0000 Hello Rowan On 24.04.09 19:56, Rowan Crowe wrote: > This is what the panic output shows: > > ------ > dev = stripe/raid10, block = 1, fs = /db > panic: ffs_blkfree: freeing free block > cpuid = 1 > GEOM_MIRROR: Device db2: rebuilding provider ad16 stopped. > GEOM_MIRROR: Device db1: rebuilding provider ad12 stopped. > Uptime: 31m16s > Physical memory: 8183 MB > Dumping: 656 MB: > > ------ Boot into single user and try to do a manual fsck on all non / file systems, probably with the -y options to automatically answer all questions like this: fsck -y Hopefully this will run to the end, it can take several hours depending on the file system size and amount of files. I have never played with gmirror, so I don't know if this will work. Eventually you also can run the gmirror check manually in single user before doing fsck. Could it be, that one of your hard disk drives starts to fail or has corrupted sectors? Eventually you see some error messages in your logfiles. bye Fabian