Date: Sat, 23 May 2015 16:24:38 -0400 From: Mahmoud Al-Qudsi <mqudsi@neosmart.net> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-stable@freebsd.org Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? Message-ID: <A5F9E3F1-4A7C-4DE5-B447-752C2909FB34@neosmart.net> In-Reply-To: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> References: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> On May 21, 2015, at 8:19 AM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > > Well, if you are just doing an NFSv4.1 mount, you could capture > packets during the failed mount attaempt with tcpdump and then > email me the raw packet capture, I can take a look at it. > (tcpdump doesn't handle nfs packets well, but wireshark will accept > a raw packet capture) Something like: > # tcpdump -s 0 -w <file>.pcap host <nfs-client> > should work. > > When I read RFC-5661 around page #567, it seems clear that the > client should use RECLAIM_COMPLETE with the fs arg false after > acquiring a noew clientid, which is what a fresh mount would normally be. > (If the packet capture shows an EXCHANGEID followed by a RECLAIM_COMPLETE > with the fs arg true, I think ESXi is broken, but I can send you a patch > that will just ignore the "true", so it works.) > I think the "true" case is only used when a file system has been "moved" > by a server cluster, indicated to the client via a NFS4ERR_MOVED error > when it is accessed at the old server, but the working in RFC-5661 isn't > very clear. > > rick Thank you kindly. I am travelling at the moment; but as soon as I can, I will get that to you. Much appreciated, Mahmoud
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A5F9E3F1-4A7C-4DE5-B447-752C2909FB34>