From owner-freebsd-current Sat Sep 27 11:23:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05753 for current-outgoing; Sat, 27 Sep 1997 11:23:24 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05748 for ; Sat, 27 Sep 1997 11:23:19 -0700 (PDT) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.5/8.8.2) with ESMTP id NAA25448; Sat, 27 Sep 1997 13:23:19 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id NAA26982; Sat, 27 Sep 1997 13:23:18 -0500 (CDT) Message-ID: <19970927132318.04053@Mars.Mcs.Net> Date: Sat, 27 Sep 1997 13:23:18 -0500 From: Karl Denninger To: Poul-Henning Kamp Cc: Karl Denninger , current@freebsd.org Subject: Re: WARNING! Builds from the last few days have BROKEN NFS References: <19970927124917.57478@Mars.Mcs.Net> <6979.875383880@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.64 In-Reply-To: <6979.875383880@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Sep 27, 1997 at 08:11:20PM +0200 Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 27, 1997 at 08:11:20PM +0200, Poul-Henning Kamp wrote: > In message <19970927124917.57478@Mars.Mcs.Net>, Karl Denninger writes: > >On Sat, Sep 27, 1997 at 08:59:19AM +0200, Poul-Henning Kamp wrote: > >> In message <19970927002623.46235@Mars.Mcs.Net>, Karl Denninger writes: > >> >WARNING! > >> > > >> >All -current builds from the last few days have BROKEN NFS client code. > >> > >> Please try > >> sysctl -w debug.wantfreevnodes=0 > >> -- > >> Poul-Henning Kamp FreeBSD coreteam member > >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > > >What effect does that cause? > > A much higher number of vnodes in the system, about half of which will > be on the freelist. This was the default until a couple of weeks ago. Uh, the problem with that Paul is that a build from the sources as they existed on the 19th does *not* exhibit the problem (which is what I'm running now). I believe that the critical change actually occurred mid-week this last week when a set of files in the vm subdirectory were modified. I'd have to go back and check out update sets for each day, one at a time, until I found the critical day, but the last set of updates which appear to have affected this all came in one batch. Do you know precisely when this was changed? -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/~karl | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex modem support is now available Voice: [+1 312 803-MCS1 x219]| 56kbps DIGITAL ISDN DOV on analog lines! Fax: [+1 312 803-4929] | 2 FULL DS-3 Internet links; 400Mbps B/W Internal