From owner-freebsd-current Fri Feb 5 15:25:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18744 for freebsd-current-outgoing; Fri, 5 Feb 1999 15:25:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18739 for ; Fri, 5 Feb 1999 15:25:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id PAA00308; Fri, 5 Feb 1999 15:25:12 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Feb 1999 15:25:12 -0800 (PST) From: Matthew Dillon Message-Id: <199902052325.PAA00308@apollo.backplane.com> To: N Cc: current@FreeBSD.ORG Subject: Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr References: <990205221457.18464A-100000@liquid.tpb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> on the NFS server before you run make install on the NFS client ). : :Actually, I did, this broke somewhere at the end of January in 3.0-STABLE. :Unfortunately I first built a kernel, rebooted with that, and tried to :build the world, but /usr/bin/ps was the wrong version so I couldn't :easily see where processes were hanging. (Can you say Catch-22 - downgrade :kernel so ps works but the bug didn't expose itself.) : :A kernel from Jan 27 works, but one dated Feb 2 doesn't. Symptoms include :a "hanging" in a random command, be it cc or install. ^Z / fg doesn't Is the Jan 27 kernel a -3.0 kernel also? How old was the CVS tree you built from the Jan 27 kernel from ? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message