Date: Tue, 6 Mar 2018 18:14:01 +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: <2feda1e2-16d5-43b5-98eb-dcc71cc67c6f@frequentis.com> In-Reply-To: <YQBPR0101MB1042040D2BFB3681E940D271DDDA0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> References: <c5c624de-42bb-45cf-8cf0-b25be56e5f58@frequentis.com> <YQBPR0101MB1042DEF0825996764CBCA829DDC40@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>, <D890568E1D8DD044AA846C56245166780124AFB90E@vie196nt> <YQBPR0101MB1042479407CAA253674BBAEBDDDB0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM> <D890568E1D8DD044AA846C56245166780124AFBD21@vie196nt>, <D890568E1D8DD044AA846C56245166780124AFBD91@vie196nt> <YQBPR0101MB104225B6884FEC70A03C61CCDDDA0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>, <D890568E1D8DD044AA846C56245166780124AFC0E2@vie196nt>, <YQBPR0101MB1042040D2BFB3681E940D271DDDA0@YQBPR0101MB1042.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, that was the main reason for using NFS 4.1. Is it planned to implement it, or is the focus on pNFS? Thanks, Andi ________________________________ Von: Rick Macklem <rmacklem@uoguelph.ca> Gesendet: 05.03.2018 11:49 nachm. An: NAGY Andreas; 'freebsd-stable@freebsd.org' Betreff: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with E= SXi client Nope, that isn't supported, rick (Hope no one is too upset by a top post.) ________________________________________ From: NAGY Andreas <Andreas.Nagy@frequentis.com> Sent: Monday, March 5, 2018 8:22:10 AM To: Rick Macklem; 'freebsd-stable@freebsd.org' Subject: RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with E= SXi client Thanks, I am actually compiling with both patches. I try now to get NFS 4.1 multipathing working. So I have now two connection= on different subnets between the ESXi host and the FreeBSD host with expor= ts for the same mountpoint on both subnets. Now I get the following errors in the vmkernel.log: 2018-03-05T13:06:07.488Z cpu10:66503)WARNING: NFS41: NFS41_Bug:2361: BUG - = Invalid BIND_CONN_TO_SESSION error: NFS4ERR_NOTSUPP Is there session trunking available in the FreeBSD NFS41 implementation? Br, andi -----Original Message----- From: Rick Macklem [mailto:rmacklem@uoguelph.ca] Sent: Montag, 5. M=E4rz 2018 02:16 To: NAGY Andreas <Andreas.Nagy@frequentis.com>; 'freebsd-stable@freebsd.org= ' <freebsd-stable@freebsd.org> Subject: Re: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with E= SXi client NAGY Andreas wrote: [stuff snipped] >In the source I saw nfs_async =3D 0; is it right that NFS will work in asy= nc 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 th= e datastore >connected via iSCSI which standard is also not sync? If you want to use it, you can just set it by setting the sysctl vfs.nfsd.a= sync=3D1. - If the server crashes/reboots you can lose data. Also, after the reboot, = the client will only see an temporarily unresponsive server and will not have= any indication of data loss. (I am not familiar with iSCSI, so I can't comment on how safe that is.) - If you are using ZFS, there is also a ZFS config (sync=3Ddisabled). I'm n= ot a ZFS guy, so I don't know anything more, but I'm sure others reading this list= can tell you how to set it. [more stuff snipped] >So far I did not see any issue with the mount. Only in the vmkernel.log th= ere are >often following entrees: >WARNING: NFS41: NFS41ValidateDelegation:608: Server returned improper >>reason for no delegation: 2 The attached patch *might* get rid of these, although I don't think it matt= ers much, since it is just complaining about the "reason" the server return= s for not issuing a delegation (issuing delegations is entirely at the disc= retion of the server and is disabled by default). [more stuff snipped] Good luck with it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2feda1e2-16d5-43b5-98eb-dcc71cc67c6f>