From owner-freebsd-hackers Thu Mar 6 05:21:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA18227 for hackers-outgoing; Thu, 6 Mar 1997 05:21:09 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA18217 for ; Thu, 6 Mar 1997 05:21:02 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA17662; Thu, 6 Mar 1997 08:20:29 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 6 Mar 1997 08:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id HAA00195 for ; Thu, 6 Mar 1997 07:30:54 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id HAA07834 for freebsd-hackers@freefall.cdrom.com; Thu, 6 Mar 1997 07:36:36 -0500 (EST) Date: Thu, 6 Mar 1997 07:36:36 -0500 (EST) From: Thomas David Rivers Message-Id: <199703061236.HAA07834@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Today's "dup alloc" info... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had just seen a posting to freebsd-hackers, where the user was running a 2.2-GAMMA kernel with DIAGNOSTIC defined; and got a vrele() panic. So, I thought; perhaps if I tried a DIAGNOSTIC kernel something would make itself apparent. (This is 2.1.6.1 sources.) Unfortunately, although this particular kernel did demonstrate the problem, no information ensued... Also, today's news-server panic was "ifree: freeing free inode". This, of course, fits with my current model where blocks are not actually written to the disk... so when the inode was allocated; it's data wasn't written. The inode was later free'd; a bread() of the particular inode gets 0 and panics and the free routine panics. [This is with an IDE machine; 386dx 8-meg, and the 2.1.6.1-RELEASE kernel Jordan built.] Just more information to "chew on." - Dave Rivers -