From owner-freebsd-fs@FreeBSD.ORG Tue Dec 13 16:25:39 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 D65AE106564A for ; Tue, 13 Dec 2011 16:25:39 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 838EA8FC0C for ; Tue, 13 Dec 2011 16:25:39 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0M7Fkw-1QmVK02CmM-00xCoj; Tue, 13 Dec 2011 17:25:38 +0100 Message-ID: <4EE77C81.1060807@brockmann-consult.de> Date: Tue, 13 Dec 2011 17:25:37 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <1888801930.136947.1323790912860.JavaMail.root@erie.cs.uoguelph.ca> <4EE77ADC.9050501@gmail.com> In-Reply-To: <4EE77ADC.9050501@gmail.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:Cqe+irjarl668+dfS2R53//XghC+YMxXTIgsIMled5n m+NM8CUFObcuP1x0ekV4/s7NUeGtp+8URlBxJOC6b00C69MsZ1 OH6OfjeW08tgAE8bwzWQkQqX6OKYzPanFK94B7LzzgfDHN91PN OKfpqdUx1ssGHAFUxCt2tTTVHDepxqH5wLdALB21CK1mNIIIfA V24/cd3QuK5gYgsbQC50T5815bP1e8wVSvur+GhZFZ4bj/pSu0 plnyVYOipDaItDMkZzsFaCR/Ty4YneyRtSB4FiPY+5U1d/A+hn Fu1MwwxgyNlDw77esJ7s15E+pXjbbBrxpoLMyg7dRL6zsXFFH0 8d/pv2Nh88tGkXAZCKUHe4mH+qrzQiTbssMl2XgNC Subject: Re: FreeBSD 9.0 and NFS async 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: Tue, 13 Dec 2011 16:25:40 -0000 On 12/13/2011 05:18 PM, Johan Hendriks wrote: > Rick Macklem schreef: >> Johan Hendriks wrote: >>> Hello all. >>> >>> I used to use async on my 8.x nfs servers! >>> On the FreeBSD 9.0 server i can not do it through the old 8.x sysctl. >>> >>> Is there an other way to set async on FreeBSD 9.x >>> >> You have two choices: >> 1 - Apply this patch to your NFS server's kernel sources and then set >> vfs.nfsd.async=1 >> http://people.freebsd.org/~rmacklem/async.patch >> >> 2 - switch to using the old server by setting >> oldnfs_server_enable="YES" >> in your /etc/rc.conf and then setting the sysctl. >> >> I'll assume that you realize that doing this violates the NFS RFCs >> because >> it runs your server in a way where there is a risk of data loss (that >> the >> client won't know to re-write) when the server crashes. >> >> rick >>> regards, >>> Johan Hendriks >>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > Yes i do know the risk. > > The thing is we want a dataset shared to a ESXi client using NFS. > I use NFS for my normal usage, (sharing ports tree and so on.) but now > we want to use it to share a ZFS dataset for a ESXi client. > We use iscsi now, but this way we miss some zfs goodies. like > snapshots(not a zvol) and most important, we can reach the files > directly. > > But with a virtual machine shared over NFS i get horrible performance. > If i copy a file to whatever virtual machine from a windows client > shared with iscsi , i get arround 80Mb per second (in the windows copy > window) almost at a steady pace. we are really pleased with that. !! > If i copy a virtual machine to the NFS share, fire it up, and do a > file copy, it never gets higher than 50 Mb and it sometimes drop to 1 > Mb then goes to 20 back to 10 and so on. > Also the machines feels sluggish in performance. > That is interesting. I am doing the same thing (and settling for the horrible 5-9MB/s writes right now with a decent ZIL that goes 65 MB/s with any other NFS sync client). But without any NFS settings, I found I can simply run: # zfs set sync=disabled tank/esxidatasetname with the same file integrity sacrifice Rick mentions above. I found that vfs.nfsd.async=1 doesn't actually do anything for me (8.2-STABLE Sept 29th). > Are there other less dangerous things i can try to boost performance? > > regards, > Johan Hendriks > > > > > > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" -- -------------------------------------------- Peter Maloney Brockmann Consult Max-Planck-Str. 2 21502 Geesthacht Germany Tel: +49 4152 889 300 Fax: +49 4152 889 333 E-mail: peter.maloney@brockmann-consult.de Internet: http://www.brockmann-consult.de --------------------------------------------