From owner-freebsd-current@FreeBSD.ORG  Sat Jan 15 19:06:53 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3C95316A4CE
	for <current@freebsd.org>; Sat, 15 Jan 2005 19:06:53 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 513D343D3F
	for <current@freebsd.org>; Sat, 15 Jan 2005 19:06:52 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0FJ6ppS009552
	for <current@freebsd.org>; Sat, 15 Jan 2005 20:06:51 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: current@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Sat, 15 Jan 2005 20:06:51 +0100
Message-ID: <9551.1105816011@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
Subject: reproduced:  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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Jan 2005 19:06:53 -0000


Quite by accident my test-machine here can now reliably reproduce
the dreaded "panic: ffs_blkfree: freeing free block" in a few minutes
of time.

It is very interesting that the location of the actual error is a
very narrow stripe of the filesystem:

	dev = ad8, block = 13456368, fs = /hex
	dev = ad8, block = 13455888, fs = /hex
	dev = ad8, block = 13454688, fs = /hex
	dev = ad8, block = 13455040, fs = /hex
	dev = ad8, block = 13455200, fs = /hex
	dev = ad8, block = 13455880, fs = /hex

The application I'm running at the time adds/modifies records in a
db(3) hash file and nothing much besides.

Before I start implementing complete I/O traces and spend days
groveling over UFS/FFS on-disk bits, are there anybody who has
suggestions for things I should try to enable/disable to narrow
this down ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.