From owner-freebsd-current@FreeBSD.ORG Mon Sep 13 01:21:26 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3830106566C for ; Mon, 13 Sep 2010 01:21:25 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id CDBC18FC0A for ; Mon, 13 Sep 2010 01:21:25 +0000 (UTC) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by fallback-in1.mxes.net (Postfix) with ESMTP id 8DA112FD7B2 for ; Sun, 12 Sep 2010 21:05:55 -0400 (EDT) Received: from [10.0.0.171] (unknown [64.9.234.55]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D1D19509DC for ; Sun, 12 Sep 2010 21:05:53 -0400 (EDT) Message-ID: <4C8D78E3.3080404@gmail.com> Date: Sun, 12 Sep 2010 18:05:39 -0700 From: David Ehrmann User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: NFS lockups with VMware esxi client X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 01:21:26 -0000 I have NFS sharing a ZFS pool that VMware esxi stores files on. When put under stress (an OS installation, but not Linux compilation), the NFS server locks, spiking to 100% CPU usage. Not even kill -KILL can stop the process, so rebooting is required. PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 885 root 4 44 0 5804K 988K CPU2 0 239:39 100.00% nfsd Other people have run into this problem, but I never found a solution. I'm running 8.1-PRERELEASE on amd64, but I think others have seen the problem on 8.1-RELEASE. zpool status reports that the pool is healthy, so that's not it. My only two ideas are hosting on something other than ZFS and trying to reproduce it with a lot of big, random NFS requests. Any other ideas?