From owner-freebsd-stable Mon Sep 25 10:12:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from beholder.2y.net (dialin-187-108.sudbury.primus.ca [216.95.187.108]) by hub.freebsd.org (Postfix) with ESMTP id 4EB9137B422 for ; Mon, 25 Sep 2000 10:12:39 -0700 (PDT) Received: from unios.dhs.org (laptop.unios.ca [192.168.0.77]) by beholder.2y.net (8.11.0/8.9.3) with ESMTP id e8PHCWZ13186 for ; Mon, 25 Sep 2000 13:12:36 -0400 (EDT) (envelope-from beholder@unios.dhs.org) Message-ID: <39CF87B4.925C6C49@unios.dhs.org> Date: Mon, 25 Sep 2000 13:13:25 -0400 From: Pat Wendorf X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: NFS Problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I've been using NFS on stable (3.x, 4.x) for a while now, and when it works, it seems to be fast and reliable. However, I've noticed that in any case where it doesn't work (nfs server goes down, cable gets disconnected, weird network card driver issues, etc), the client machines seem to get stuck in an nfs-read state limbo of some sort. My poor laptop was in this state for about 3 days and the daily run's (find in particular) was hung (new hung "find" every day). If I could kill these processes off, I probably wouldn't mind, but these processes simply do not die (even kill -9), without a reboot. The worst part is, while they are hung, I cannot unmount the NFS share (says it's being used). The shutdown isn't clean either because it cannot kill them at shutdown time. Is this normal behavior, and if so, how do I stop it from happening? If this is something I've misconfigured I can provide hardware and config file details on request. Thanks for any help :) -- Pat Wendorf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message