From owner-freebsd-bugs@FreeBSD.ORG Wed Jul 23 08:00:11 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C658106567F for ; Wed, 23 Jul 2008 08:00:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5008A8FC17 for ; Wed, 23 Jul 2008 08:00:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6N80BAs043786 for ; Wed, 23 Jul 2008 08:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6N80BaH043785; Wed, 23 Jul 2008 08:00:11 GMT (envelope-from gnats) Resent-Date: Wed, 23 Jul 2008 08:00:11 GMT Resent-Message-Id: <200807230800.m6N80BaH043785@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Luis Soltero Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F207106564A for ; Wed, 23 Jul 2008 07:59:11 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 2E37E8FC27 for ; Wed, 23 Jul 2008 07:59:11 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m6N7xABQ014349 for ; Wed, 23 Jul 2008 07:59:10 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id m6N7xATS014348; Wed, 23 Jul 2008 07:59:10 GMT (envelope-from nobody) Message-Id: <200807230759.m6N7xATS014348@www.freebsd.org> Date: Wed, 23 Jul 2008 07:59:10 GMT From: Luis Soltero To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/125895: kernel: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2008 08:00:11 -0000 >Number: 125895 >Category: kern >Synopsis: kernel: panic: ffs_blkfree: freeing free block >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Jul 23 08:00:10 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Luis Soltero >Release: FreeBSD 6.3 >Organization: Global Marine Networks, LLC >Environment: FreeBSD mail2.gmn-usa.com 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #0: Wed Feb 13 00:11:33 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/SMP amd64 >Description: The problem has been noticed on FreeBSD 6.2-RELEASE-p5 and FreeBSD 6.3 We first noted the problem when we wanted to backup our FreeBSD 6.2 to 6.3 using sh freebsd-update.sh -f freebsd-update.conf -r 6.3-RELEASE upgrade as suggested in the 6.3 release Announcement. After successfully completing a dump of a live file system using dump -0Lf - /usr > /home/dumps/usr.dump the system panic with Jul 23 06:13:41 mail2 syslogd: kernel boot file is /boot/kernel/kernel Jul 23 06:13:41 mail2 kernel: dev = da0s1d, block = 1, fs = /usr Jul 23 06:13:41 mail2 kernel: panic: ffs_blkfree: freeing free block Jul 23 06:13:41 mail2 kernel: cpuid = 0 Jul 23 06:13:41 mail2 kernel: Uptime: 44m25s Jul 23 06:13:41 mail2 kernel: Cannot dump. No dump device defined. Jul 23 06:13:41 mail2 kernel: Automatic reboot in 15 seconds - press a key on the console to abort Jul 23 06:13:41 mail2 kernel: Rebooting... This bug resembles a previously reported bug http://www.jp.freebsd.org/cgi/query-pr.cgi?pr=kern/116913 for FreeBSD 7.0. We believe this to be the same problem. Our suspicion is that the panic happens when a large block of data on a file system mounted with soft updates is removed. In our case the snap shot created by the -L option to dump cause the system to panic right after the dump completes and the system removes the snapshot file. This thread seems to be discussing the same problem http://www.mavetju.org/mail/view_message.php?list=freebsd-current&id=2546411 other links of interest http://freebsd.monkey.org/freebsd-current/200710/threads.html#00196 >How-To-Repeat: dump -0Lf - /usr > /home/dumps/usr.dump on a live system running the release version of FreeBSD 6.3 >Fix: A quick search of the internet suggests that the problem can be fixed by disabling soft updates for a file system. after disabling softupdates for /usr the dump no longer causes a panic. Thanks, --luis >Release-Note: >Audit-Trail: >Unformatted: