From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 13:20:24 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 74C6016A4EE for ; Tue, 11 Nov 2003 13:20:20 -0800 (PST) Received: from smaug.vex.net (H211.C136.B246.tor.eicat.ca [66.246.136.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C5EF43F3F for ; Tue, 11 Nov 2003 13:20:19 -0800 (PST) (envelope-from x@Vex.Net) Received: from bee.vii.net (unknown [209.135.116.67]) by smaug.vex.net (Postfix) with ESMTP id E7DC64856C for ; Tue, 11 Nov 2003 16:20:19 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by bee.vii.net (Postfix) with ESMTP id 3C9C05C80 for ; Tue, 11 Nov 2003 16:20:14 -0500 (EST) From: Tim Middleton Organization: xxvii.net To: current@freebsd.org Date: Tue, 11 Nov 2003 16:20:13 -0500 User-Agent: KMail/1.5.4 References: <200311101744.hAAHiefC008462@spider.deepcore.dk> In-Reply-To: <200311101744.hAAHiefC008462@spider.deepcore.dk> X-Whee: Yes, Please. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311111620.13378.x@Vex.Net> Subject: Re: Still getting NFS client locking up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: current@freebsd.org 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:20:24 -0000 On November 10, 2003 12:44 pm, Soren Schmidt wrote: > For me its just the server end that fails, I've not seen the client hang. I'm having a bad NFS day... not sure if it is the same lockups described in this thread. In fact perhaps I'm posting to the wrong group since the server in questoin is 4.9-STABLE. The client I am testing with is 5.1-CURRENT (though a few months old) however. I'm trying to make sure this server is stable, as it took a long time to get my company to let me switch one of the servers to FreeBSD... things were going great until i started testing NFS... now they are going very badly. I can lock the NFS server up every time simply by mounting the nfs partition (i'm using -t for tcp nfs and exporting with -maproot=0:0), and then running "iozone -a" on the nfs client box. It takes a while, but the 4.9-RELEASE box will always lock up solid eventually. Not good. )-: I've done tests as root and non-root. Sometimes i can rescue the nfs client box with a "mount -f", but sometimes the client box has locked up solid as well when I've tried that. The server is a P3-1ghz Intel STL2 box, with 1 gig of ram. Using the onboard fxp ethernet at 100baseTX. It is not using dhcp. Nothing much else is running on this server box as I'm just testing it. When the server locks the box can not even be pinged. Since the box locks up solid its hard to see what may be going on. I have left top running to see what it says when it freezes, but it may not be accurate depending on when it last refreshed. But for the record it has nfsd in "biorw" state. I tried dumping ps -lax to a file every few seconds while testing... that didn't work very well as again the refresh is too slow, and the drive loses the last few files when it goes down. Perhaps I can turn off caching or soft updates or something to help with this (as you may tell, i'm not a file systme expert --- any suggestions, welcome). Maybe I should set up another box and test 4.9-RELEASE to 4.9-RELEASE... and/or update my 5.1-CURRENT box for further testing... -- Tim Middleton | Cain Gang Ltd | One afternoon, disgusted, bravo, you fall x@veX.net | www.Vex.Net | asleep. --T.Lilburn (MS)