From owner-freebsd-current Tue Mar 30 15:13: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 357F114C2D for ; Tue, 30 Mar 1999 15:12:57 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id SAA28065; Tue, 30 Mar 1999 18:21:44 -0500 (EST) Date: Tue, 30 Mar 1999 18:21:43 -0500 (EST) From: Alfred Perlstein To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: nfs problems In-Reply-To: <199903302249.AAA10220@wurzelausix.cs.uni-sb.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 31 Mar 1999, Thomas Schuerger wrote: > Hi! > > I'm experiencing serious NFS problems, when > a remote NFS directory (also on FreeBSD) mounted on my > machine goes down for whatever reason (e.g. normal > shutdown). From then on, any processes accessing the mounted > NFS directory (e.g. executing ls or even df) will die and stay > non-removable (kill -9 shows no effect on them!) in the system. > If the remote server goes up again, then sometimes these > processes work again. > > I wonder if this is a general problem of NFS or just a > problem with FreeBSD (haven't checked it with non-current > machines). Any ideas/fixes? This is freebsd following the NFS spec, please read the mount_nfs man page for the workaround (hint: intr). Check out the ORA book on NFS and NIS, it's quite good. -Alfred > > > Ciao, > Thomas. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Alfred Perlstein - Admin, coder, and admirer of all things BSD. -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message