From owner-freebsd-hackers  Tue Mar 11 19:20:44 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA08795
          for hackers-outgoing; Tue, 11 Mar 1997 19:20:44 -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 TAA08782
          for <freebsd-hackers@freefall.FreeBSD.org>; Tue, 11 Mar 1997 19:20:40 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA20995; Tue, 11 Mar 1997 22:20:08 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 11 Mar 1997 22: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 VAA07037; Tue, 11 Mar 1997 21:38:32 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id VAA24869; Tue, 11 Mar 1997 21:44:35 -0500 (EST)
Date: Tue, 11 Mar 1997 21:44:35 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199703120244.VAA24869@lakes.water.net>
To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.water.net!rivers,
        ponds!lambert.org!terry
Subject: Re: 2.2-GAMMA (3/10/97) and the "dup alloc" problem.
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Just to follow-up on my own mail...

> 
> > 
> > > Just to report in on the question of "does the latest
> > > 2.2-GAMMA (3/10/97) exhibit the 'dup alloc' problem".
> > > 
> > > I have just tried out the boot floppies that were made this 
> > > morning; the problem still exists.
> > 
> > Have you tried disabling the directory name cache in kern/vfs_cache.c yet?
> > 
> > 
> > 					Regards,
> > 					Terry Lambert
> > 					terry@lambert.org
> 
>  Hmm.. nope; I've been persuing missing splbio()s and what-not; [not
> too successfully I might add.]
> 
>  What makes you consider this a possibility - just for my own edification.
> I wouldn't have thought that came into play on a newfs'd file system...
> Are you suggesting the cache lookup is returning the wrong vnode somewhere?
> 
>  And, apparently this can all be disable (in the 2.1.6.1 sources)
> by setting "doingcache" to 0.. is that what you're thinking of?
> 
> 	- Dave Rivers -

  I set "doingcache" to 0 in vfs_cache.c; and reran the test (again,
this is 2.1.6.1).

  Unfortunately, the test still fails - that is, the error is still
manifest.

	- Dave Rivers -