Date: Thu, 04 Oct 2007 20:48:13 -0500 From: Eric Anderson <anderson@freebsd.org> To: avleeuwen@piwebs.com Cc: Peter Jeremy <peterjeremy@optushome.com.au>, Current@freebsd.org Subject: Re: panic: ffs_blkfree: freeing free block Message-ID: <470597DD.6080909@freebsd.org> In-Reply-To: <d86b48730710031306h54925166u5a5e943ef21e9a22@mail.gmail.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470597DD.6080909>