Date: Mon, 25 Sep 2000 10:38:03 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Pat Wendorf <beholder@unios.dhs.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS Problems Message-ID: <20000925103803.X9141@fw.wintelcom.net> In-Reply-To: <39CF87B4.925C6C49@unios.dhs.org>; from beholder@unios.dhs.org on Mon, Sep 25, 2000 at 01:13:25PM -0400 References: <39CF87B4.925C6C49@unios.dhs.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Pat Wendorf <beholder@unios.dhs.org> [000925 10:13] wrote: > 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 :) You probably want to mount your NFS with the 'intr' and 'soft' options. see the mount_nfs manpage. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000925103803.X9141>