From: Rick Macklem <rmacklem@uoguelph.ca>
To: "andreas-nagy@outlook.com" <andreas-nagy@outlook.com>,
"crispyduck@outlook.at" <crispyduck@outlook.at>,
"J. Bruce Fields" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: Chuck Lever III <chuck.lever@oracle.com>
Subject: Re: Problems with NFS4.1 on ESXi
Date: Thu, 5 May 2022 14:19:12 +0000 [thread overview]
Message-ID: <YT2PR01MB97309F3F3B856591D633162CDDC29@YT2PR01MB9730.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AM9P191MB1665FA51F62F82B006FD97168EC29@AM9P191MB1665.EURP191.PROD.OUTLOOK.COM>
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@outlook.com <andreas-nagy@outlook.com>
Sent: Thursday, May 5, 2022 1:31 AM
To: crispyduck@outlook.at; Rick Macklem; J. Bruce Fields; linux-nfs@vger.kernel.org
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@uoguelph.ca
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@outlook.at <crispyduck@outlook.at>
Gesendet: Mittwoch, 27. April 2022 08:08
An: Rick Macklem <rmacklem@uoguelph.ca>; J. Bruce Fields <bfields@fieldses.org>; linux-nfs@vger.kernel.org <linux-nfs@vger.kernel.org>
Cc: Chuck Lever III <chuck.lever@oracle.com>
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@uoguelph.ca>
Gesendet: Sonntag, 24. April 2022 22:39
An: J. Bruce Fields <bfields@fieldses.org>
Cc: crispyduck@outlook.at <crispyduck@outlook.at>; Chuck Lever III <chuck.lever@oracle.com>; Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Betreff: Re: Problems with NFS4.1 on ESXi
Rick Macklem <rmacklem@uoguelph.ca> 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.
next prev parent reply other threads:[~2022-05-05 14:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9P191MB1665484E1EFD2088D22C2E2F8EF59@AM9P191MB1665.EURP191.PROD.OUTLOOK.COM>
2022-04-21 4:55 ` Problems with NFS4.1 on ESXi Andreas Nagy
2022-04-21 14:58 ` Chuck Lever III
2022-04-21 15:30 ` AW: " crispyduck
2022-04-21 16:40 ` J. Bruce Fields
[not found] ` <AM9P191MB16654F5B7541CD1E489D75608EF49@AM9P191MB1665.EURP191.PROD.OUTLOOK.COM>
2022-04-21 18:41 ` crispyduck
2022-04-21 18:54 ` J. Bruce Fields
2022-04-21 23:52 ` Rick Macklem
2022-04-21 23:58 ` Rick Macklem
2022-04-22 14:29 ` Chuck Lever III
2022-04-22 14:59 ` AW: " crispyduck
2022-04-22 15:02 ` Chuck Lever III
2022-04-22 22:58 ` Rick Macklem
2022-04-22 15:15 ` J. Bruce Fields
2022-04-22 18:43 ` AW: " crispyduck
2022-04-22 23:03 ` Rick Macklem
2022-04-24 15:07 ` J. Bruce Fields
2022-04-24 20:36 ` Rick Macklem
2022-04-24 20:39 ` Rick Macklem
2022-04-25 9:00 ` AW: " crispyduck
2022-04-27 6:08 ` crispyduck
2022-05-05 5:31 ` andreas-nagy
2022-05-05 14:19 ` Rick Macklem [this message]
2022-05-05 16:38 ` Chuck Lever III
2022-05-07 1:53 ` Chuck Lever III
2022-04-22 14:23 ` Olga Kornievskaia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YT2PR01MB97309F3F3B856591D633162CDDC29@YT2PR01MB9730.CANPRD01.PROD.OUTLOOK.COM \
--to=rmacklem@uoguelph.ca \
--cc=andreas-nagy@outlook.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=crispyduck@outlook.at \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).