From owner-freebsd-smp Thu Nov 22 5:24:18 2001 Delivered-To: freebsd-smp@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 17C6937B416 for ; Thu, 22 Nov 2001 05:24:09 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Nov 2001 13:24:08 +0000 (GMT) To: Yoriaki FUJIMORI Cc: freebsd-smp@freebsd.org Subject: Re: nfsd/ypserv die on smp In-Reply-To: Your message of "Thu, 22 Nov 2001 22:01:24 +0900." <200111221301.fAMD1Ow10621@prinz.fujimori.cache.waseda.ac.jp> Date: Thu, 22 Nov 2001 13:24:07 +0000 From: Ian Dowse Message-ID: <200111221324.aa00865@salmon.maths.tcd.ie> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <200111221301.fAMD1Ow10621@prinz.fujimori.cache.waseda.ac.jp>, Yoria ki FUJIMORI writes: > >I have to correct some of my reports. >The time stamp of nfsd which is dead is wrong. >Theire date do not match the date of corresponding nfsiod. >Their date which appears in `lastcomm nfsd' result line is just >much older than now, I have to say. >Something is wrong on smp of 4.4R, though. It would be useful if you could capture a ktrace dump of what happens when the nfsd exits. That should provide a few hints about why it is exiting. The easiest way to do this would be to kill all the nfsd's and then run: ktrace -i nfsd -u -t -n 10 Then, whenever you see an nfsd exit, stop the tracing ("ktrace -C"), and use kdump to look for the last few things the nfsd did before it exited. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message