From owner-freebsd-current@FreeBSD.ORG  Fri May  2 16:39:26 2003
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 AAC8137B40B; Fri,  2 May 2003 16:39:26 -0700 (PDT)
Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1C4C243F3F; Fri,  2 May 2003 16:39:26 -0700 (PDT)
	(envelope-from mckusick@beastie.mckusick.com)
Received: from beastie.mckusick.com (localhost [127.0.0.1])
	by beastie.mckusick.com (8.12.8/8.12.3) with ESMTP id h42NdOTh011519;
	Fri, 2 May 2003 16:39:24 -0700 (PDT)
	(envelope-from mckusick@beastie.mckusick.com)
Message-Id: <200305022339.h42NdOTh011519@beastie.mckusick.com>
To: Robert Watson <rwatson@FreeBSD.org>
In-Reply-To: Your message of "Fri, 02 May 2003 18:16:16 EDT."
             <Pine.NEB.3.96L.1030502175131.4408g-200000@fledge.watson.org> 
Date: Fri, 02 May 2003 16:39:24 -0700
From: Kirk McKusick <mckusick@beastie.mckusick.com>
cc: Ian Dowse <iedowse@maths.tcd.ie>
cc: jeff@FreeBSD.org
cc: current@FreeBSD.org
cc: Scott Long <scott_long@btc.adaptec.com>
Subject: Re: ffs_blkfree: freeing free block -- ps, traces, fsck log 
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: Fri, 02 May 2003 23:39:27 -0000

My last checkin was in mid-March, so I am highly suspicious that
someone else has done something to create this problem. Unfortunately,
this panic comes about because of something that caused the bitmaps
to get trashed sometime (possibly much) earlier. The usual suspects
are updates to the bitmap that are failing (e.g., the I/O is not
being done), or in-memory trashing (e.g., wild pointers). Given the
nature of the fsck output, it looks like bitmap updates that are not
being properly done. A good quick test is to mount a filesystem, add
some files to it, unmount it and run fsck to see if any discrepencies
show up. As the unmount sometimes forces writes that would otherwise
fail, running a background fsck on it (fsck_ffs -B /foo) will 
sometimes show the problem a bit better.

	Kirk McKusick