From owner-freebsd-stable@freebsd.org Sun Mar 4 18:22:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52E7EF24753 for ; Sun, 4 Mar 2018 18:22:16 +0000 (UTC) (envelope-from Andreas.Nagy@frequentis.com) Received: from mail2.frequentis.com (mail2.frequentis.com [195.20.158.51]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "spamquarantine.frequentis.frq", Issuer "Frequentis Enterprise Issuing CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F463680EB for ; Sun, 4 Mar 2018 18:22:14 +0000 (UTC) (envelope-from Andreas.Nagy@frequentis.com) X-IronPort-AV: E=Sophos;i="5.47,424,1515452400"; d="scan'208";a="2430998" Received: from vie190nt.frequentis.frq ([172.16.1.190]) by mail2.frequentis.com with ESMTP; 04 Mar 2018 19:22:07 +0100 Received: from vie196nt.frequentis.frq ([172.16.1.196]) by vie190nt.frequentis.frq ([172.16.1.190]) with mapi id 14.03.0382.000; Sun, 4 Mar 2018 19:22:07 +0100 From: NAGY Andreas To: 'Rick Macklem' , "'freebsd-stable@freebsd.org'" Subject: =?iso-8859-1?Q?RE:_NFS_4.1_RECLAIM=5FCOMPLETE_FS=A0failed_error_in_combin?= =?iso-8859-1?Q?ation_with_ESXi_client?= Thread-Topic: =?iso-8859-1?Q?NFS_4.1_RECLAIM=5FCOMPLETE_FS=A0failed_error_in_combinatio?= =?iso-8859-1?Q?n_with_ESXi_client?= Thread-Index: AdOx8zAe5+TceuOWQkax+IhJZhNDgQAnzopHABn27/AAIBzCQgAP8SUgAAmzYWA= Date: Sun, 4 Mar 2018 18:22:06 +0000 Message-ID: References: , In-Reply-To: Accept-Language: de-AT, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.12.22] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 18:22:16 -0000 Okay, the slow write was not a NFS problem, it was the hw raid controller w= hich switched to write through because of a broken battery. In the source I saw nfs_async =3D 0; is it right that NFS will work in asyn= c mode if I compile the kernel with nfs_async =3D 1? I know the risk of running it async, but is it not the same risk having the= datastore connected via iSCSI which standard is also not sync? The last weeks I tested the following setup: Two FreeBSD hosts with a more or less good hw RAID controller in a HAST clu= ster providing a datastore to two ESXi hosts via iSCSI. This setup worked quiet well, but I now want to switch to NFS, and hope to = get equivalent speeds. Thanks so far, andi =20 -----Original Message----- From: NAGY Andreas=20 Sent: Sonntag, 4. M=E4rz 2018 14:26 To: Rick Macklem ; freebsd-stable@freebsd.org Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS=A0failed error in combination with= ESXi client Thanks, got it working with your patch. So far I did not see any issue with the mount. Only in the vmkernel.log the= re are often following entrees: WARNING: NFS41: NFS41ValidateDelegation:608: Server returned improper reaso= n for no delegation: 2 Actually I have only a single link between the ESXi host and the FreeBSD ho= st, but as soon as I figure out what Is the right way to configure multiple= paths for NFS I will do more testing.=20 I need also to check out what can be tuned. I expected that writes to the N= FS datastore will be slower than iSCSI but not as slow as it is now. andi=20 -----Original Message----- From: Rick Macklem [mailto:rmacklem@uoguelph.ca] Sent: Sonntag, 4. M=E4rz 2018 06:48 To: NAGY Andreas ; freebsd-stable@freebsd.org Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS=A0failed error in combination with= ESXi client NAGY Andreas wrote: >Hi and thanks! > >First time using/needing a patch could you give me a short advise how to u= se it >and for which version? The only difference with kernel versions will be the line#s. >So far I have made a fresh FreeBSD 11.1 RELEASE install as a VM on a=20 >ESXi host >updated the system and did a svn checkout=20 >http://svn.freebsd.org/base/release/11.1.0/ > >Then tried to apply the patch in /usr/src/sys via patch <=20 >/tmp/reclaimcom2.patch > >Output was: >Hmm... Looks like a unified diff to me... >The text leading up to this was: >-------------------------- >|--- fs/nfsserver/nfs_nfsdserv.c.savrecl 2018-02-10 20:34:31.166445= 000 -0500 >|+++ fs/nfsserver/nfs_nfsdserv.c 2018-02-10 20:36:07.947490000 -050= 0 >-------------------------- >Patching file fs/nfsserver/nfs_nfsdserv.c using Plan A... >No such line 4225 in input file, ignoring Hunk #1 succeeded at 4019=20 >(offset -207 lines). >done Since it says "Hunk #1 succeeded...", I think it patched ok. However, you can check by looking at nfsrvd_reclaimcomplete() in sys/fs/nfs= server/nfs_nfsdserv.c. Before the patch it would look like: if (*tl =3D=3D newnfs_true) nd->nd_repstat =3D NFSERR_NOTSUPP; else nd->nd_repstat =3D nfsrv_checkreclaimcomplete(nd); wherea= s after being patched, it will look like: nd->nd_repstat =3D nfsrv_checkreclaimcomplete(nd); if (*tl =3D=3D newnfs_true) nd->nd_repstat =3D 0; rick [stuff snipped]