From owner-freebsd-fs@FreeBSD.ORG Wed Apr 27 20:10:53 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 104F21065670 for ; Wed, 27 Apr 2011 20:10:53 +0000 (UTC) (envelope-from cforgeron@acsi.ca) Received: from mta04.eastlink.ca (mta04.eastlink.ca [24.224.136.10]) by mx1.freebsd.org (Postfix) with ESMTP id CC6958FC0C for ; Wed, 27 Apr 2011 20:10:52 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from ip01.eastlink.ca ([unknown] [24.222.39.10]) by mta04.eastlink.ca (Sun Java(tm) System Messaging Server 7.3-11.01 64bit (built Sep 1 2009)) with ESMTP id <0LKB00AMYUQ3A1S0@mta04.eastlink.ca> for freebsd-fs@freebsd.org; Wed, 27 Apr 2011 17:10:51 -0300 (ADT) X-CMAE-Score: 0 X-CMAE-Analysis: v=1.1 cv=mORQtGzMSGJSBwuMSvVfB0MKjPGmXehAuj88Uvu04o4= c=1 sm=1 a=e8U4T-BRE4EA:10 a=IkcTkHD0fZMA:10 a=QYf_FK3ziJuEyJ82DQgA:9 a=QEXdDO2ut3YA:10 a=E/PVjAe7IbPkHCM0BPV0xg==:117 Received: from blk-222-10-85.eastlink.ca (HELO server7.acsi.ca) ([24.222.10.85]) by ip01.eastlink.ca with ESMTP; Wed, 27 Apr 2011 17:10:51 -0300 Received: from server7.acsi.ca ([192.168.9.7]) by server7.acsi.ca ([192.168.9.7]) with mapi; Wed, 27 Apr 2011 17:10:49 -0300 From: Chris Forgeron To: Rick Macklem Date: Wed, 27 Apr 2011 17:10:46 -0300 Thread-topic: make the experimental NFS subsystem the default one Thread-index: AcwAKbxaQ/MyU6P1QY+So9wY48H1MgE7GykQ Message-id: References: <1143723691.393441.1303384281461.JavaMail.root@erie.cs.uoguelph.ca> In-reply-to: <1143723691.393441.1303384281461.JavaMail.root@erie.cs.uoguelph.ca> Accept-Language: en-US Content-language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US 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: Wed, 27 Apr 2011 20:10:53 -0000 Yes, as I noted in my message, you can't enable async client side - It's inside of ESX, and you don't have an option to modify. And yes, it would also mean that you could really screw things up, but even if you have to make it a hidden option, I know it would be invaluable to the ESX crowd. When you're running on a ZFS storage base, having sync writes in NFS doesn't add any security, as ZFS is handling all of that for us, and often with far more performance/reliability. I think it would give a nice advantage to a FreeBSD ZFS/NFS solution. It definitely makes a speed difference, even with a properly configured ZIL. Would it be enough to have a big warning on the man page for the switch that it breaks RFC compliance, to log that warning when it happens, and to generally warn of dire consequences to anyone who doesn't understand what they are doing? Otherwise I just have to hack up the source and release a patch to those who want the feature, which seems counterproductive. I'd be very appreciative of the switch, and can offer you some heavy testing of it and your NFS code and report back to help with your code adoption. -----Original Message----- From: Rick Macklem [mailto:rmacklem@uoguelph.ca] Sent: Thursday, April 21, 2011 8:11 AM 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