Date: Tue, 11 Mar 1997 21:44:35 -0500 (EST) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> 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. Message-ID: <199703120244.VAA24869@lakes.water.net>
next in thread | raw e-mail | index | archive | help
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 -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703120244.VAA24869>