From owner-freebsd-stable Mon Sep 25 23:43:13 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 D613037B422 for ; Mon, 25 Sep 2000 23:43:02 -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 e8Q6guZ15117; Tue, 26 Sep 2000 02:42:56 -0400 (EDT) (envelope-from beholder@unios.dhs.org) Message-ID: <39D045A1.CA0035C3@unios.dhs.org> Date: Tue, 26 Sep 2000 02:43:45 -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: Alfred Perlstein Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS Problems References: <39CF87B4.925C6C49@unios.dhs.org> <20000925103803.X9141@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Pat Wendorf [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. > Thanks Alfred, this did clear up the problem with the machine hanging, and now I believe I'm getting some interesting log messages that may clear up why I've been experiencing this more often than normal: Sep 26 02:28:17 laptop /kernel: nfs_getpages: error 4 Sep 26 02:28:17 laptop /kernel: vm_fault: pager read error, pid 1047 (cp) Sep 26 02:28:52 laptop /kernel: nfs_getpages: error 4 Sep 26 02:28:52 laptop /kernel: vm_fault: pager read error, pid 1053 (cp) Sep 26 02:35:34 laptop /kernel: nfs_getpages: error 4 Sep 26 02:35:34 laptop /kernel: vm_fault: pager read error, pid 1100 (cp) Sep 26 02:36:28 laptop /kernel: nfs_getpages: error 4 Sep 26 02:36:28 laptop /kernel: vm_fault: pager read error, pid 1112 (cp) Sep 26 02:37:04 laptop /kernel: nfs_getpages: error 4 Sep 26 02:37:04 laptop /kernel: vm_fault: pager read error, pid 1118 (cp) My syslog on my laptop keeps repeating this every time I try to do any major I/O on the NFS mount (but thankfully, now I can break out of the cp command when it hangs). The server end doesn't seem to be complaining, just the client end. Thanks again for any help :) -- Pat Wendorf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message