From owner-freebsd-stable Sun Feb 28 21:30:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 512BA151A3 for ; Sun, 28 Feb 1999 21:30:11 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id XAA14161 for stable@freebsd.org; Sun, 28 Feb 1999 23:29:55 -0600 (CST) From: Joe Greco Message-Id: <199903010529.XAA14161@aurora.sol.net> Subject: Any known NFS problems in 3.1R? To: stable@freebsd.org Date: Sun, 28 Feb 1999 23:29:54 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a pet project which involves Diablo (news transit) and NFS. Hi Matt. DSRS is a search engine that NFS mounts a Diablo spool and proceeds to build databases of various interesting information. I recently did an upgrade to 3.1R on the host running DSRS, and all was well for about a day. Now, twice, I've found the machine stuck in a twilight state. Any running processes continue to run (such as my watchdog-card daemon, top on a vty, etc) but the instant any disk access is attempted, the process joins the rest of the system in a grand hang. At least, this is what it appears to be. "top" reports that the processes are stuck in "inode". Other processes such as "snmpd" which are not apparently stuck in inode may be gunned down (thanks to the kill in "top"), but a kill -TERM 1 has no effect even after several minutes. The NFS server is a slightly-pre-3.0R machine, and will probably get itself upgraded tonight. What information should I be looking for to help me figure out what is happening? ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message