Date: Fri, 20 Aug 1999 20:18:27 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: freebsd-stable@freebsd.org Subject: Re: vm_fault: pager read error on NFS filesystems. Message-ID: <19990820201827.A22891@lanczos.maths.tcd.ie> In-Reply-To: <199908171256.aa44534@salmon.maths.tcd.ie>; from David Malone on Tue, Aug 17, 1999 at 12:56:17PM %2B0100 References: <199908171256.aa44534@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 17, 1999 at 12:56:17PM +0100, David Malone wrote: > When a user deletes/changes a running executable over NFS it results > in lots of "vm_fault: pager read error" messages. However, the > program seems to keep running indefinitely, and logging messages. > Someone running a parrallel program recompiled and added 184888 > lines to /var/log/messages in a little over an hour. Following up my own message on this. On two machines on which we had a "vm_fault: pager read error" problem init ended up stuck in state vmopar while reaping one of the processes! Eventually the machine became overwhelemed by Zombies (Sounds very "Night of the Living Dead"), and we had to reboot. If it happens again I'll try to get a dump. I do have the output of ps for a stuck machine if anyone wants to see it, but basically a process whose image was changed overs NFS is the lowest numbered zombie and there are loads of processes waiting for init to reap them. David. 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?19990820201827.A22891>