From owner-freebsd-fs@FreeBSD.ORG Fri Oct 8 11:00:34 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 1E81A106566B for ; Fri, 8 Oct 2010 11:00:34 +0000 (UTC) (envelope-from marco@tolstoy.tols.org) Received: from tolstoy.tols.org (tolstoy.tols.org [IPv6:2a02:898:0:20::57:1]) by mx1.freebsd.org (Postfix) with ESMTP id A855E8FC22 for ; Fri, 8 Oct 2010 11:00:33 +0000 (UTC) Received: from tolstoy.tols.org (localhost [127.0.0.1]) by tolstoy.tols.org (8.14.4/8.14.4) with ESMTP id o98B0Unn096343; Fri, 8 Oct 2010 11:00:30 GMT (envelope-from marco@tolstoy.tols.org) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.96.3 at tolstoy.tols.org Received: (from marco@localhost) by tolstoy.tols.org (8.14.4/8.14.4/Submit) id o98B0UXn096342; Fri, 8 Oct 2010 13:00:30 +0200 (CEST) (envelope-from marco) Date: Fri, 8 Oct 2010 13:00:30 +0200 From: Marco van Tol To: gil@vidals.net Message-ID: <20101008110030.GD94234@tolstoy.tols.org> Mail-Followup-To: gil@vidals.net, freebsd-fs@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on tolstoy.tols.org 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: Fri, 08 Oct 2010 11:00:34 -0000 On Fri, Oct 08, 2010 at 03:00:28AM -0700, Gil Vidals wrote: > I'm hoping that somebody can help me as I've spent about a month studying > FreeBSD + ZFS to use as a NAS for my VMware ESX environment; however, it > looks like my hopes were completely dashed yesterday as my ZFS server based > on 64-bit i7 CPU with 8 GB of RAM and SSD slogs came crumbling down when I > added a second NFS mount point. > > After several hours of research on the crash, it seems that FreeBSD 8.1 > won't launch more than one nfsd, no matter what is configured in rc.conf. > (FreeBSD 7.x does launch multiple NFS daemons). So when I added my second > mount point, the CPU load went very high for the RPC services and the second > NFS mount point disconnected, brining down the running VMs. Check out the '-n' flag to nfsd, which is defaulted to 4 in /etc/defaults/rc.conf through nfs_server_flags. > PROBLEM: only one nfsd > zambia# ps waux | grep nfs > root 1213 0.0 0.0 5804 1508 ?? Is 5:23PM 0:00.02 nfsd: master > (nfsd) > root 1214 0.0 0.0 5804 1588 ?? S 5:23PM 8:06.88 nfsd: server > (nfsd) Try this one with 'ps Hjax | grep nfs'. The capital H is used to display threads next to processes. Add w flags to ps if necessary. > 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 haven't got much experience with nfs4, sorry. :) Marco -- Most general statements are false, including this one. - Alexander Dumas