From owner-freebsd-stable Fri Feb 25 3:35:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6609637BB09 for ; Fri, 25 Feb 2000 03:35:36 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Feb 2000 11:35:35 +0000 (GMT) Date: Fri, 25 Feb 2000 11:35:32 +0000 From: David Malone To: Ilya Obshadko Cc: stable@freebsd.org Subject: Re: NFS client lockup? Message-ID: <20000225113532.A49913@walton.maths.tcd.ie> References: <6843.000224@zhurnal.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <6843.000224@zhurnal.ru>; from ilya@zhurnal.ru on Thu, Feb 24, 2000 at 08:14:30PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 24, 2000 at 08:14:30PM +0300, Ilya Obshadko wrote: > 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. Your best hope of finding what the problem, is to compile in the kernel debugger and leave yourself on the text console. When the machine locks up break to the debugger and get a trace, it can be worth doing this a few times by continuing the kernel and getting another trace so you can try to figure out where in the code the kernel is stuck. We've managed to diagnose problems like this fairly quickly as long as the problem is fairly easy to reproduce. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message