From owner-freebsd-current@FreeBSD.ORG  Fri Oct  5 01:48:31 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: Current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D8DDC16A468
	for <Current@freebsd.org>; Fri,  5 Oct 2007 01:48:31 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com
	[72.36.161.186])
	by mx1.freebsd.org (Postfix) with ESMTP id 765F713C4D9
	for <Current@freebsd.org>; Fri,  5 Oct 2007 01:48:31 +0000 (UTC)
	(envelope-from anderson@freebsd.org)
Received: from proton.local
	(r74-193-81-203.pfvlcmta01.grtntx.tl.dh.suddenlink.net
	[74.193.81.203]) (authenticated bits=0)
	by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id l951mKUx038885;
	Thu, 4 Oct 2007 20:48:25 -0500 (CDT)
	(envelope-from anderson@freebsd.org)
Message-ID: <470597DD.6080909@freebsd.org>
Date: Thu, 04 Oct 2007 20:48:13 -0500
From: Eric Anderson <anderson@freebsd.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: avleeuwen@piwebs.com
References: <1191175387.92510.6.camel@shumai.marcuscom.com>	<46FFF615.5090108@donut.de>	<d86b48730710010628q6259c661xaae5b0848c4ef1ed@mail.gmail.com>	<d86b48730710030621w5692aeb7tb4074a701c554b41@mail.gmail.com>	<20071003195644.GN80294@turion.vk2pj.dyndns.org>
	<d86b48730710031306h54925166u5a5e943ef21e9a22@mail.gmail.com>
In-Reply-To: <d86b48730710031306h54925166u5a5e943ef21e9a22@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com
Cc: Peter Jeremy <peterjeremy@optushome.com.au>, Current@freebsd.org
Subject: Re: panic: ffs_blkfree: freeing free block
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 05 Oct 2007 01:48:31 -0000

Arjan van Leeuwen wrote:
> 2007/10/3, Peter Jeremy <peterjeremy@optushome.com.au>:
>> On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen <avleeuwen@gmail.com>
>> wrote:
>>> Also, I note that everytime I panic, my currently opened files are
>> reduced
>>> to 0 bytes. Is that expected?
>> It depends, are you talking about files being read or only files being
>> written?  If this is just affecting writes, then this is a side-effect
>> of the stdio buffering, together with the write-back nature of the UFS
>> buffer cache in conjunction with soft-updates: Data on disk is
>> typically about 30 seconds behind reality and the file contents will
>> always be behind the file itself.  It is quite normal for recently
>> written files (or files currently being written) to be truncated on
>> disk following a crash.
> 
> Yep, these are recently written files indeed. Usually the files I had open
> in my editor while it paniced, files that I save often.
> Oh well... I'm setting my hopes on this panic being resolved soon then :).
> Thanks for the explanation.

Can anyone provide access to the core dumps?

Eric