From owner-freebsd-current@FreeBSD.ORG Wed Oct 3 19:56:50 2007 Return-Path: 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 1F68F16A418 for ; Wed, 3 Oct 2007 19:56:50 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mx1.freebsd.org (Postfix) with ESMTP id 6CCE413C46A for ; Wed, 3 Oct 2007 19:56:49 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l93Jui8O035120; Thu, 4 Oct 2007 05:56:44 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l93JuiwR035119; Thu, 4 Oct 2007 05:56:44 +1000 (EST) (envelope-from peter) Date: Thu, 4 Oct 2007 05:56:44 +1000 From: Peter Jeremy To: avleeuwen@piwebs.com Message-ID: <20071003195644.GN80294@turion.vk2pj.dyndns.org> References: <1191175387.92510.6.camel@shumai.marcuscom.com> <46FFF615.5090108@donut.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mvpLiMfbWzRoNl4x" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Oct 2007 19:56:50 -0000 --mvpLiMfbWzRoNl4x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen wrot= e: >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. --=20 Peter Jeremy --mvpLiMfbWzRoNl4x Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHA/P8/opHv/APuIcRApCLAJ4tqWbULAZlB3cnxZzSbB8aq5kCNQCePFhU sx98WbrQCTkxzkeDjctlU4k= =x5tr -----END PGP SIGNATURE----- --mvpLiMfbWzRoNl4x--