Date: Wed, 5 May 1999 01:35:16 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Doug Rabson <dfr@nlsystems.com>, Kevin Day <toasty@home.dragondata.com>, jso@research.att.com, hackers@FreeBSD.ORG Subject: Re: kern/11470: V3 NFS problem (fwd) Message-ID: <Pine.BSF.3.96.990505012925.7628B-100000@cygnus.rush.net> In-Reply-To: <199905041842.LAA18532@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 May 1999, Matthew Dillon wrote: > :2) If I set a cpu time limit for a process, and the executable file is being > :ran over NFS, if it exceeds the CPU limit, i get flooded with "vm_fault: pager > :error"'s > > This is definitely a bug. I'll bet you are using an 'intr' or 'soft' > mount, yes? There are still some serious bugs with 'intr' mounts > interacting badly with the VM system, but they should be relatively easy > to fix. > > :3) See PR 7728. NFS server is also a web server, dumping logs into user's > :home directories. Our FTP server is an NFS client. When clients try to > :download their log files, the ftpd process gets stuck (kill -9 won't kill > :it). This also happens when they try to upload over top of a file they just > :viewed on the web server. > : > :Processes seem to get stuck in 'sbwait' (which really doesn't seem like it's > :stuck), or 'nfsrcv' > > What is occuring is that existing VM cache pages are being ripped out from > under the client and the client is getting confused. I'll need to work > up a reliable way to reproduce the problem between a client and server > in order to squash it. If someone else can come up with a simple script > to run on the client & the server that reproduces the problem, we will > be able to squash it more quickly. just grab some huge program like 'wine' (i can provide a binary if you want it) and run the program over 10mbit (or serial?) NFS on two slow machines... and delete the binary before it gets entirely paged in? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990505012925.7628B-100000>