From owner-freebsd-current Sat Sep 27 12:56:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09834 for current-outgoing; Sat, 27 Sep 1997 12:56:20 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09821 for ; Sat, 27 Sep 1997 12:56:15 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA13500; Sat, 27 Sep 1997 21:55:23 +0200 (CEST) To: Karl Denninger cc: Nate Williams , current@freebsd.org Subject: Re: WARNING! Builds from the last few days have BROKEN NFS In-reply-to: Your message of "Sat, 27 Sep 1997 14:51:32 CDT." <19970927145131.64000@Mars.Mcs.Net> Date: Sat, 27 Sep 1997 21:55:23 +0200 Message-ID: <13496.875390123@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> 'Just do it, and quit 'yer arguing' :) :) :) :) > >What I don't understand is why this kind of change would have the effect >that it is having. That is, why would reducing the target number of vnodes >on the freelist lead to hangs in a disk wait ("D") which are unkillable? Karl, neither do any of us at this time. We may be pretty good wizards, but we're not gods any of us. We need more data, and that involves you doing as we say in an attempt to figure out what the heck is going on. I'm running a make buildworld across NFS right now, but so far I see no trouble along the lines of what you found. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop."