From owner-freebsd-current@FreeBSD.ORG Wed Nov 12 14:38:25 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 548AD16A4CE for ; Wed, 12 Nov 2003 14:38:25 -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 3830F43FE3 for ; Wed, 12 Nov 2003 14:38:24 -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 BB28648599 for ; Wed, 12 Nov 2003 17:38:24 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by bee.vii.net (Postfix) with ESMTP id A05B85C7A for ; Wed, 12 Nov 2003 17:38:14 -0500 (EST) From: Tim Middleton Organization: xxvii.net To: freebsd-current@freebsd.org Date: Wed, 12 Nov 2003 17:38:13 -0500 User-Agent: KMail/1.5.4 References: <200311112149.hABLnZeF070361@gw.catspoiler.org> <3FB1B8B3.8090403@bgp4.net> In-Reply-To: <3FB1B8B3.8090403@bgp4.net> 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: <200311121738.13783.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: freebsd-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: Wed, 12 Nov 2003 22:38:25 -0000 On November 11, 2003 11:36 pm, Janet Sullivan wrote: > So far I only have problems in a mixed -STABLE/-CURRENT environment. > When the client & server are both -CURRENT I haven't had any problems. I just installed another -STABLE box to see if keeping them both -STABLE helps. I haven't really tested the NFS yet as I didn't want to risk locking the box up in the middle of a buildworld. So i just mounted the NFS drive on the new test box and left it.... Within an hour the NFS server box doing the build world was locked up solid. I can't say if it was NFS mount related or not; nfsd wasn't really doing anything. Doesn't seem like it would have been. Beginning to wonder if it is some strange hardware problem on this box; which coincidentally only shows up when there's an nfs mount! But that doesn't explain why my normally rock solid desktop system tanked when being tested as an NFS client to that STABLE box. Hmmm... Back to testing. I'm doing heavy disk I/O tests without any NFS mounts now. If they go okay, back to the NFS mounting and testing... It seems to me there is something desperately wrong with NFS is mixing -CURRENT and -STABLE NFS server/clients causes either side (in my case both sides) to lock up solid. I mean, problems are problems... but solid lockups with no crash messages or anything is ... nasty. > Are the folks seeing hangs getting any kind of console error messages? I see nothing. My server is completely locks up. Nothing responds. The drive light (the times i've noticed) is frozen "on". On my desktop box the mouse is dead as well. > I don't see anything - performance just tanks to the point of being > unusable. When testing with my desktop box as client, i noticed just before or just when the NFS locked up the mouse and keyboard response would be very erratic ... slow and jerky. -- Tim Middleton | Cain Gang Ltd | "Who is Ungit?" said he, still holding x@veX.net | www.Vex.Net | my hands. --C.S.Lewis (TWHF)