From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 13:49:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E06F16A543 for ; Tue, 11 Nov 2003 13:49:51 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 621CB43F85 for ; Tue, 11 Nov 2003 13:49:50 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id hABLnZeF070361; Tue, 11 Nov 2003 13:49:47 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200311112149.hABLnZeF070361@gw.catspoiler.org> Date: Tue, 11 Nov 2003 13:49:35 -0800 (PST) From: Don Lewis To: schnozzy@verbotenplanet.net In-Reply-To: <0.66385300.1067603499@verbotenplanet.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: freebsd-current@FreeBSD.org Subject: Re: Still getting NFS client locking up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 21:49:51 -0000 On 31 Oct, Kelley Reynolds wrote: > --- Original Message --- > From: Matt Smith > Sent: Fri, 31 Oct 2003 08:55:49 +0000 > To: Robert Watson > Subject: Re: Still gettnig NFS client locking up > >> Robert Watson wrote: >> > On Tue, 28 Oct 2003, Soren Schmidt wrote: >> > >> > >> >>>I'm now running a kernel/world of October 26th on both NFS client >> >>>and server machines. I am still seeing NFS lockups as reported by >> >>>several people in these threads: >> >> >> >>Me too!! >> > >> > >> > Hmm. I'm unable to reproduce this so far, and I'm pounding several >> > 5.x NFS clients and servers. I've been checking out using CVS over >> > NFS, performing dd's of big files, etc. There must be something >> > more I'm missing in reproducing this. What network interface cards >> > are you using (client, server)? Are you using DHCP on the client or >> > server? What commands trigger it -- what part of the NFS >> > namespace, etc? Are you running the commands as root, or another >> > user? >> > >> > Robert N M Watson FreeBSD Core Team, TrustedBSD >> > Projects robert@fledge.watson.org Network Associates >> > Laboratories >> > > > I'm also experiencing lockups with NFS, but it's the server that locks > up on mine. Both client and server are -CURRENT. Server was fresh as > of two days ago, and the client is a week or two old. They are > connected via bfe (server) and vr (client). The server, I've found, > will last much longer if the mount options on the client include 'tcp' > and 'nfsv3' (supposed to be default, but I'm just calling it like it > is). Reading files seems to be okay, and I've managed to get as far as > compiling a kernel on an NFS-mounted /usr, but a buildworld will hang > in < 30 minutes. The server is running dhcp and pf. All commands are > being run as root. I'm not having any problems with my -CURRENT client. My server is running 4.9-STABLE, so I can't comment on the state of the NFS server code in -CURRENT. For what it's worth, my NFS usage is not very heavy, and is mostly reading, with very little writing.