From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 12:47:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65C3516A41A for ; Thu, 11 Oct 2007 12:47:51 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb5:7e66]) by mx1.freebsd.org (Postfix) with ESMTP id E242D13C442 for ; Thu, 11 Oct 2007 12:47:50 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id l9BAPtHh001913 for ; Thu, 11 Oct 2007 12:25:56 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org Date: Thu, 11 Oct 2007 12:25:55 +0200 User-Agent: KMail/1.9.7 References: <1191175387.92510.6.camel@shumai.marcuscom.com> <470597DD.6080909@freebsd.org> <200710110215.24824.pieter@degoeje.nl> In-Reply-To: <200710110215.24824.pieter@degoeje.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710111225.55719.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No 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: Thu, 11 Oct 2007 12:47:51 -0000 On Thursday 11 October 2007, Pieter de Goeje wrote: > On Friday 05 October 2007, Eric Anderson wrote: > > Arjan van Leeuwen wrote: > > > 2007/10/3, Peter Jeremy : > > >> On 2007-Oct-03 15:21:15 +0200, Arjan van Leeuwen > > >> > > >> 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. This address is no longer valid. Eric, if you are reading this, I've sent you mail with the correct address :D. > > uname -a: > FreeBSD unforgiven.student.utwente.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #8: > Mon Oct 8 01:48:17 CEST 2007 > pyotr@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