From owner-freebsd-fs@FreeBSD.ORG Thu Apr 21 11:11:22 2011 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 924D71065672 for ; Thu, 21 Apr 2011 11:11:22 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 4C1848FC19 for ; Thu, 21 Apr 2011 11:11:21 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAGkQsE2DaFvO/2dsb2JhbACEUaFviHCrCZB8gSmDUH0Ejis X-IronPort-AV: E=Sophos;i="4.64,251,1301889600"; d="scan'208";a="119079905" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 21 Apr 2011 07:11:21 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 7BB93B3F28; Thu, 21 Apr 2011 07:11:21 -0400 (EDT) Date: Thu, 21 Apr 2011 07:11:21 -0400 (EDT) From: Rick Macklem To: Chris Forgeron Message-ID: <1143723691.393441.1303384281461.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: make the experimental NFS subsystem the default one 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: Thu, 21 Apr 2011 11:11:22 -0000 > > I've hacked up the old NFS server a bit to better serve my ESX/NFS > needs (forcing it to always write async so it works faster with ZFS > and a ZIL). I guess I could do the same to the new code as well... > > ..However, if you didn't mind adding switch to force the NFS server to > quietly only do an async VOP_WRITE, that would be really handy. Very > dangerous for some people, but then again, so are most switches if you > don't understand what they do. ESX will only opens it's files with > O_SYNC, and it's not an editable option, so people like me running > ESX+NFS over a ZFS share that has a ZIL are making the system do a lot > of unnecessary sync writes. Yes, I know about SSD/RAM for the ZIL, but > it still slows it down quite a bit over an async write. Have you tries the "async" mount option on the client side? (or did you say you couldn't do that above?) I would be very hesitant to do it on the server side, since it would violate the RFC (and you do run a risk of losing data, which many might not realize uptil it is too late). rick