From owner-freebsd-stable Thu Feb 24 9:11: 3 2000 Delivered-To: freebsd-stable@freebsd.org Received: from me.ru (shell.me.ru [194.247.134.139]) by hub.freebsd.org (Postfix) with ESMTP id 12CE237BDEA for ; Thu, 24 Feb 2000 09:10:56 -0800 (PST) (envelope-from ilya@zhurnal.ru) Received: from [194.247.147.206] (HELO webmaster.zhurnal.ru) by me.ru (CommuniGate Pro SMTP 3.2) with ESMTP id 137897 for stable@freebsd.org; Thu, 24 Feb 2000 20:10:54 +0300 Date: Thu, 24 Feb 2000 20:14:30 +0300 From: Ilya Obshadko X-Mailer: The Bat! (v1.39) Educational Reply-To: Ilya Obshadko Organization: Zhurnal.RU X-Priority: 3 (Normal) Message-ID: <6843.000224@zhurnal.ru> To: stable@freebsd.org Subject: NFS client lockup? 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 Hello, I've experienced NFS client lockup that hangs entire box. There is no any diagnostic messages, network interface is active (I can ping the system), but system is not responding at all, I'm unable to reboot it with Ctrl-Alt-Del. This occurs only under high NFS-mounted filesystem load with concurrent read/write requests. At the moment of lockup, top shows processes that use NFS in "nfsrcv" state. Does anybody knows what is this? Can NFS server be responsible for that? (NFS server is Solaris 7/x86, it doesn't produce any error messages too). I'm running: FreeBSD 3.4-RC #25: Fri Dec 10 19:16:55 MSK 1999 Best regards, Ilya mailto:ilya@zhurnal.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message