Date: Thu, 4 Oct 2007 05:56:44 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: avleeuwen@piwebs.com Cc: Current@freebsd.org Subject: Re: panic: ffs_blkfree: freeing free block Message-ID: <20071003195644.GN80294@turion.vk2pj.dyndns.org> In-Reply-To: <d86b48730710030621w5692aeb7tb4074a701c554b41@mail.gmail.com> References: <1191175387.92510.6.camel@shumai.marcuscom.com> <46FFF615.5090108@donut.de> <d86b48730710010628q6259c661xaae5b0848c4ef1ed@mail.gmail.com> <d86b48730710030621w5692aeb7tb4074a701c554b41@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <avleeuwen@gmail.com> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071003195644.GN80294>