Re: panic: ffs_blkfree: freeing free block

On Friday 05 October 2007, Eric Anderson wrote:
> Arjan van Leeuwen wrote:
> > 2007/10/3, Peter Jeremy <peterjeremy_at_optushome.com.au>:
> >> On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen <avleeuwen_at_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?

Hi Eric,

I've put a coredump and kernel.debug at 
http://lux.student.utwente.nl/~pyotr/panic/ along with the dmesg and kernel 
configuration file.

uname -a:
FreeBSD unforgiven.student.utwente.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #8: Mon 
Oct  8 01:48:17 CEST 2007     
pyotr_at_unforgiven.student.utwente.nl:/usr/obj/usr/src/sys/UNFORGIVEN  amd64

I am not sure about the security impact of putting a coredump in a public 
place, so I didn't cc current. ("Somewhat" less public this way...)

The panic often occurs while doing
# portsnap fetch update
# portversion -vl \<

If you need anything else please let me know.

With kind regards,
Pieter de Goeje