From owner-freebsd-fs@FreeBSD.ORG Wed Nov 9 14:20:21 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 2A3F4106567A for ; Wed, 9 Nov 2011 14:20:21 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A908E8FC21 for ; Wed, 9 Nov 2011 14:20:20 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1RO90l-0002nb-7A for freebsd-fs@freebsd.org; Wed, 09 Nov 2011 15:20:19 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Nov 2011 15:20:19 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Nov 2011 15:20:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Wed, 09 Nov 2011 15:20:05 +0100 Lines: 50 Message-ID: References: <1558351773.1229453.1320542285788.JavaMail.root@erie.cs.uoguelph.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig35D83D6A50AA795B73594029" X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1 In-Reply-To: <1558351773.1229453.1320542285788.JavaMail.root@erie.cs.uoguelph.ca> X-Enigmail-Version: 1.1.2 Subject: Re: [RFC] Should vfs.nfsrv.async be implemented for new NFS server? 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, 09 Nov 2011 14:20:21 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig35D83D6A50AA795B73594029 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 06/11/2011 02:18, Rick Macklem wrote: > Hi, >=20 > Josh Paetzel pointed out that vfs.nfsrv.async doesn't exist > for the new NFS server. >=20 > I don't think I had spotted this before, but when I looked I > saw that, when vfs.nfsrv.async is set non-zero in the old server, > it returns FILESYNC (which means the write has been committed to > non-volatile storage) even when it hasn't actually done that. Do I understand this correctly: the server normally (for async=3D0) does = a fsync after any writes and returns FILESYNC status to the client? This seems too extreme... doesn't NFSv4 have its own fsync()-like RPC that does that manually? If it does, then I don't think there are any differences between doing a write() on a local file system with e.g. soft-updates enabled and doing a write on a NFS file system - in both cases, no data is even remotely guaranteed to survive a crash unless a fsync (or equivalent operation) was issued. On 06/11/2011 17:25, Josh Paetzel wrote: > In 8.x, setting the async sysctl was the difference between 80-100MB/se= c > and 800 MB/sec (Yes, MegaBytes!) using a variety of different clients, Yup, this is in any case too big not to add the async mode. --------------enig35D83D6A50AA795B73594029 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk66jBUACgkQldnAQVacBchbtwCgk7wbUqaY08vOSwU+OYYvWuqr XtMAoJWCJgg2AkWcrrQ8TyEpHt1JAR99 =LcwZ -----END PGP SIGNATURE----- --------------enig35D83D6A50AA795B73594029--