I have made some more traces, one time with nfs3 and one time with nfs41: uploaded here: https://easyupload.io/7bt624 Both from mount till start of vm import (testvm). NFS3 works, NFS41 fails. exportfs -v: /zfstank/sto1/ds110 <world>(async,wdelay,hide,crossmnt,no_subtree_check,fsid=74345722,mountpoint,sec=sys,rw,secure,no_root_squash,no_all_squash) I tried it now many times, but was not able to reproduce a "good" case with nfs41. Tests with FreeBSD I can do when I am back from my business trip, As I need to add some disks to the servers. regards, Andreas Von: Rick Macklem <rmacklem@xxxxxxxxxxx> Gesendet: Sonntag, 24. April 2022 22:39 An: J. Bruce Fields <bfields@xxxxxxxxxxxx> Cc: crispyduck@xxxxxxxxxx <crispyduck@xxxxxxxxxx>; Chuck Lever III <chuck.lever@xxxxxxxxxx>; Linux NFS Mailing List <linux-nfs@xxxxxxxxxxxxxxx> Betreff: Re: Problems with NFS4.1 on ESXi Rick Macklem <rmacklem@xxxxxxxxxxx> wrote: [stuff snipped] > In FreeBSD, it actually hangs onto the parent's FH (verbatim), but mostly > so it can do Open/Claim_NULLs for it. There is nothing in FreeBSD that > tries to subvert FH guessing. Oops, this is client side, not server side. (I forgot which hat I was wearing;-) The FreeBSD server does not keep track of parents. rick --b.
