From owner-freebsd-hackers Sat Feb 7 09:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05286 for hackers-outgoing; Sat, 7 Feb 1998 09:33:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05260 for ; Sat, 7 Feb 1998 09:33:00 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (max2-143.HiWAAY.net [208.147.145.143]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id LAA06468 for ; Sat, 7 Feb 1998 11:32:57 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id KAA20198 for ; Sat, 7 Feb 1998 10:13:37 -0600 (CST) Message-Id: <199802071613.KAA20198@nospam.hiwaay.net> X-Mailer: exmh version 2.0.1 12/23/97 To: hackers@FreeBSD.ORG From: David Kelly Subject: Re: More NFS Problems In-reply-to: Message from "Evan Champion" of "Fri, 06 Feb 1998 21:29:30 EST." <02b601bd3370$386d8fe0$2844c00a@cello.synapse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Feb 1998 10:13:37 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe hackers" Evan Champion writes: > > I am always able to recover the system without rebooting by killing the > offending processes and restarting them. However, each of my systems does > not run a large number of different tasks, so it is relatively easy to guess > what to kill on each system. On a larger system, it might be just a lot > easier to restart. > > Irrespective, I don't think it should be doing that :-) Me too. I don't have this problem with Solaris or Irix NFS. Even if the filesystem is busy, "umount -k /filesystem" will close it in Irix, even if the remote system is not responding. But I don't think its just offending processes keeping the system blocked in FreeBSD. I used to put NFS mounts in /etc/fstab without the noauto option until I got tired of "df" blocking forever if the server was not responding. Have never been able to umount a non-responding NFS fs on FreeBSD short of a reboot. Currently I use amd to mount NFS filesystems. Replace what used to be the mount point with a symbolic link to /host/{hostname}/{filesystem} and it works as it always has. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.