From owner-freebsd-fs@FreeBSD.ORG Sat Oct 9 21:31:31 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEAE1106564A for ; Sat, 9 Oct 2010 21:31:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD098FC0A for ; Sat, 9 Oct 2010 21:31:31 +0000 (UTC) X-AuditID: 1209190f-b7c1dae000000a2b-9e-4cb0dbb051fe Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-4.mit.edu (Symantec Brightmail Gateway) with SMTP id F2.2C.02603.0BBD0BC4; Sat, 9 Oct 2010 17:16:32 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id o99LGSCL018079; Sat, 9 Oct 2010 17:16:29 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o99LGQjn001255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 9 Oct 2010 17:16:27 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id o99LGPRn016770; Sat, 9 Oct 2010 17:16:25 -0400 (EDT) Date: Sat, 9 Oct 2010 17:16:25 -0400 (EDT) From: Benjamin Kaduk To: gil@vidals.net In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: AAAAAA== Cc: freebsd-fs@freebsd.org Subject: Re: moving away from freebsd and zfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2010 21:31:31 -0000 On Fri, 8 Oct 2010, Gil Vidals wrote: > The solution described here, > http://forums.freebsd.org/showthread.php?t=11873 points to compiling a > kernel with these options: > > options NFSD > options DEVICE_POLLING > options HZ=1000 > > The NFSD seems to be what solved the problem for the forum poster, but NFSD > option means that NFSv4 (experimental) is what is running and that isn't > supported by the VMware NFS client, so I can't use it. I don't know what to > do and I would be grateful for any suggestions. I thought that the experimental server can speak both NFSv4 and NFSv3 -- have you actually tried using it and had the VMware client fail to talk to it? It seems that one can specify the -e argument to nfsd and skip the kernel rebuild, if I am reading the man page correctly ... -Ben Kaduk