Date: Sat, 3 Mar 2018 14:36:49 +0000 From: NAGY Andreas <Andreas.Nagy@frequentis.com> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-stable@freebsd.org" <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?= Message-ID: <D890568E1D8DD044AA846C56245166780124AFB90E@vie196nt> In-Reply-To: <YQBPR0101MB1042DEF0825996764CBCA829DDC40@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> References: <c5c624de-42bb-45cf-8cf0-b25be56e5f58@frequentis.com> <YQBPR0101MB1042DEF0825996764CBCA829DDC40@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi and thanks! First time using/needing a patch could you give me a short advise how to us= e it and for which version? So far I have made a fresh FreeBSD 11.1 RELEASE install as a VM on a ESXi h= ost updated the system and did a svn checkout http://svn.freebsd.org/base/r= elease/11.1.0/ Then tried to apply the patch in /usr/src/sys via patch < /tmp/reclaimcom2.= patch Output was:=20 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.1664450= 00 -0500 |+++ fs/nfsserver/nfs_nfsdserv.c 2018-02-10 20:36:07.947490000 -0500 -------------------------- Patching file fs/nfsserver/nfs_nfsdserv.c using Plan A... No such line 4225 in input file, ignoring Hunk #1 succeeded at 4019 (offset -207 lines). done So I think this was not correct, as I also noticed that nfs_nfsdserv.c 4102= lines. andi -----Original Message----- From: Rick Macklem [mailto:rmacklem@uoguelph.ca]=20 Sent: Samstag, 3. M=E4rz 2018 03:01 To: NAGY Andreas <Andreas.Nagy@frequentis.com>; freebsd-stable@freebsd.org Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS=A0failed error in combination with= ESXi client NAGY Andreas wrote: >I am trying to get a FreeBSD NFS 4.1 export working with VMware Esxi 6.5u1= , but >it is always mounted as read only. > >After some research, I found out that this is a known problem, and there a= re >threads about this from 2015 also in the mailinglist archive. > >As it seems VMware will not change the bahvior of there NFS 4.1 client I w= anted >to ask here if there is a patch or workaround for this available. I believe the attached small patch deals with the ReclaimComplete issue. However, someone else who tested this had additional issues with the mount: - The client logged a couple of things (that sounded weird to me;-) - Something about Readdir seeing directories change too much.. - Something about "wrong reason for not issuing a delegation"... (I don't what either of these are caused by or whether they result in seri= ous breakage of the mount.) They also ran into a hang when transferring a large file. It sounded to me = like something that might be a network interface device driver issue and I = suggested they disable TSO, LRO and jumbo frames, but I never heard back fr= om them, so I don't know more about this. So, feel free to test with the attached patch and if you run into problems = with the mount, email w.r.t. what they are. If we persevere we might get it= going ok. rick [stuff snipped]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D890568E1D8DD044AA846C56245166780124AFB90E>