freebsd stable - Mar 2018 - RE: NFS 4.1 RECLAIM_COMPLETE FS failed error in combination with ESXi client

NAGY Andreas wrote:
>>I'll take another look and see if I can guess why it doesn't
like "2" as a reason for >not issuing a delegation. (As noted
before, I don't think this is serious, but???)
>
>This warnings are still there, but don't seem to have any impact. It
looks like they >only appeare when files are created or modified on the
datastore from the >datastore browser or from shell, have not seen this
warnings when working in a >VM on a virtual disk that is stored on the nfs
datastore.
I've attached one more little patch. If this one is applied after
wantdeleg.patch
and wantdeleg2.patch it might get rid of these. (There was another place
that needed to be changed that got missed by wantdeleg.patch.)

Have fun with it, rick

-------------- next part --------------
A non-text attachment was scrubbed...
Name: wantdeleg3.patch
Type: application/octet-stream
Size: 1197 bytes
Desc: wantdeleg3.patch
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20180310/266fcc53/attachment.obj>

Thanks, the not issuing delegation warnings disappeared with this patch.

But now there are some new warnings I haven't seen so far:
2018-03-10T13:01:39.441Z cpu8:68046)WARNING: NFS41: NFS41FSOpGetObject:2148:
Failed to get object 0x43910e71b386 [36 c6b10167 9b157f95 5aa100fb 8ffcf2c1 c 2
9f22ad6d 0 0 0 0 0]: Stale file handle

These only appear several times after a the NFS share is mounted or remounted
after a connection loss.
Everything works fine, but haven't seen them till I applied the last patch.

andi