From owner-freebsd-hackers@FreeBSD.ORG  Thu Jul 29 09:57:21 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BFE021065670
	for <freebsd-hackers@freebsd.org>; Thu, 29 Jul 2010 09:57:21 +0000 (UTC)
	(envelope-from rhfb@akira.stdio.com)
Received: from akira.stdio.com (akira.stdio.com [204.152.114.29])
	by mx1.freebsd.org (Postfix) with SMTP id 8C5848FC18
	for <freebsd-hackers@freebsd.org>; Thu, 29 Jul 2010 09:57:11 +0000 (UTC)
Received: from akira (localhost [127.0.0.1])
	by akira.stdio.com (Postfix) with SMTP id AD3F3C2
	for <freebsd-hackers@freebsd.org>; Thu, 29 Jul 2010 05:39:58 -0400 (EDT)
Date: Thu Jul 29 05:41:06 EDT 2010
In-Reply-To: <AANLkTi=3LKv4DkaX_yHo5WfXK33YGYSAaOvqh5mjSVTV@mail.gmail.com>
From: <rhfb@akira.stdio.com> 
To: <freebsd-hackers@freebsd.org>
References: <AANLkTinUVKByfTX+f9DOQ97jh43VPVSug_=BDpJ9PB0z@mail.gmail.com>
	<AANLkTi=3LKv4DkaX_yHo5WfXK33YGYSAaOvqh5mjSVTV@mail.gmail.com>
Message-Id: <20100729094046.AD3F3C2@akira.stdio.com>
Subject: (no subject)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2010 09:57:21 -0000

I have a similar problem.

I have a NFS server (8.0 upgraded a couple times since Feb 2010) that locks up
and requires a reboot.

The clients are busy vm's from VMWare ESXi using the NFS server for vmdk virtual
disk storage.

The ESXi reports nfs server inactive and all the vm's post disk write errors when
trying to write to their disk.

/etc/rc.d/nfsd restart fails to work (it can not kill the nfsd process)

The nfsd process runs at 100% cpu at rc_lo state in top.

reboot is the only fix.

It has only happened under two circumstances.
1) Installation of a VM using Windows 2008.
2) Migrating 16 million mail messages from a physical server to a VM running FreeBSD with ZFS file system as a VM on the ESXi box that uses NFS to store the VM's ZFS disk.

The NFS server uses ZFS also.