Date: Sun, 17 Jun 2018 16:49:27 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "andreas.nagy@frequentis.com" <andreas.nagy@frequentis.com> Subject: Re: NFSv4.1 server deficiencies fixed for ESXi client Message-ID: <YTOPR0101MB09535E4234A66628849352A2DD720@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <201806171442.w5HEg3pB060542@pdx.rh.CN85.dnsmgr.net> References: <YTOPR0101MB0953EACBFD7354D0CAA44C8EDD720@YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM>, <201806171442.w5HEg3pB060542@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes wrote: [stuff snipped] >Have you any contact with VMWare so that they might fix the issues >in their code, rather than having to put hacks in FreeBSD for these >issues? Nope. I tried an email to nfsv4@ietf.org about one issue (that isn't yet re= solved related to it complaining that a directory changes too many times when stuf= f is being deleted from it) in the hopes that someone that worked on the client would respond, but no one made any technical comments on the post. Andreas mentioned that his company might have some sort of maintenance agreement so he could give them a bug report, but I don't think he's had an= y opportunity to do that? To be honest, I'm amazed it works with any NFSv4.1 server, but apparently i= t does? So if anyone can get the list of problems in the "ESXi NFSv4.1 client is na= sty" post to VMware's engineering people, it would be appreciated. Thanks, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTOPR0101MB09535E4234A66628849352A2DD720>