From owner-freebsd-hackers Thu Feb 17 16:16:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 2A6FE37B893 for ; Thu, 17 Feb 2000 16:16:36 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@one.cs.rpi.edu [128.213.14.1]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA04080 for ; Thu, 17 Feb 2000 19:16:35 -0500 (EST) Message-Id: <200002180016.TAA04080@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: stuck NFS procs Date: Thu, 17 Feb 2000 19:16:34 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is only the second time ever this has happened, but it is still an interesting problem... I have a large number of "emacs" processes stuck in disk-wait. Here is the ps axl line for one such process: 33639 88194 1 0 -22 0 5856 340 vmpfw D qi- 0:01.34 emacs proxy. Any attempt to access emacs on the client system would result in a type of hang for that process. Here is a 'cat /usr/local/bin/emacs >/dev/null': 2371 90317 1 3 -18 0 268 8 pgtblk D p4- 0:00.02 cat /usr/loc To "fix" this I went to the NFS server and 'cp emacs emacs.new;rm emacs;mv emacs.new emacs'. In essence forcing a new FH. The old procs still stick arround. This leads me to believe the problem is entirely on the local system (ie, the kernel isn't asking for pages from the NFS server for that FH) Any ideas what could be corrupting the local cache (I am assuming that is the problem) like this. Nothing of note in the dmesg. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message