I took a quick look at the 4.1 capture, but did not see anything that would explain the problem. There appears to be several Read requests near the end of the capture that do not have replies in the capture, but that was all I saw that looked unusual. rick ________________________________________ From: andreas-nagy@xxxxxxxxxxx <andreas-nagy@xxxxxxxxxxx> Sent: Thursday, May 5, 2022 1:31 AM To: crispyduck@xxxxxxxxxx; Rick Macklem; J. Bruce Fields; linux-nfs@xxxxxxxxxxxxxxx Cc: Chuck Lever III Subject: AW: Problems with NFS4.1 on ESXi CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp@xxxxxxxxxxx Hi, was someone able to check the NFS3 vs NFS4.1 traces (https://easyupload.io/7bt624)? I was due to quarantine I was so far not able to test it against FreeBSD. Would it maybe make any difference updating the Ubuntu based Linux kernel from 5.13 to 5.15? Br Andreas Von: crispyduck@xxxxxxxxxx <crispyduck@xxxxxxxxxx> Gesendet: Mittwoch, 27. April 2022 08:08 An: Rick Macklem <rmacklem@xxxxxxxxxxx>; J. Bruce Fields <bfields@xxxxxxxxxxxx>; linux-nfs@xxxxxxxxxxxxxxx <linux-nfs@xxxxxxxxxxxxxxx> Cc: Chuck Lever III <chuck.lever@xxxxxxxxxx> Betreff: AW: Problems with NFS4.1 on ESXi I tried again to reproduce the "sometimes working" case, but at the moment it always fails. No Idea why it in the past sometimes worked. Why are this much lookups in the trace? Dont see this on other NFS clients. The traces with nfs3 where it works and nfs41 where it always fails are here: https://easyupload.io/7bt624 Both from mount till start of vm import (testvm). 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 hope I can also do some tests against a FreeBSD server end of the week. 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.
