From owner-freebsd-isp Sun Jan 4 13:50:34 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA28804 for isp-outgoing; Sun, 4 Jan 1998 13:50:34 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA28793 for ; Sun, 4 Jan 1998 13:50:26 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.7/8.8.5) with SMTP id QAA22636; Sun, 4 Jan 1998 16:50:19 -0500 (EST) Date: Sun, 4 Jan 1998 16:50:19 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: jbutt@mwci.net cc: freebsd-isp@freebsd.org Subject: Re: [fbsd-isp] Designing for a very large ISP In-Reply-To: <199801042025.OAA22797@subcellar.mwci.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > How stable is the NFS in FreeBSD.. I know that BSDI 2.0 had some real > NFS problems (escapes me now as to what they were). Is the NFS in > FreeBSD just as stable as the SUN's ect.. We've not yet used it widely, as we still see problems with lockups or panics. I'm upgrading about 10 machines tomorrow to stable from a few days ago to see if the old problems are still there. We're currently running stable from a month or so ago and see behaviour like this: Start an nfs mount, either v3 or v2, UDP or TCP Leave client mounted Get rid of server by either killing mountd, pulling net access, or shutting down the machine Execute either mount or df on Client At this point we see different behaviour. The client sometimes panics (haven't been at the console to see why), or the command hangs and is un-killable. The only way to get rid of the phantom mount seems to be a reboot of the client.... Seems to work well except for this behaviour, but I wouldn't want to put it in production. After the upgrade tomorrow, I'll repeat while at the console to see what happens. FWIW, I haven't seen this on 2.1.7. It takes some work to get the mount back, but usually doesn't require a boot of the client to clear the "stale" mount... Charles > ----------------------------------------------------------- > James 'J.D.' Butt Voice 319.557.8463 > Network Engineer pager 319.557.6347 > MidWest Communications, Inc. fax 319.557.9771 > 241 Main St. noc@mwci.net > Dubuque, IA 52001 jbutt@mwci.net > ----------------------------------------------------------- > "I used up all my sick days... so I'm calling in dead" > "Lets fight against continental drift!" >