From: Rick Macklem <rmacklem@uoguelph.ca>
To: "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>
Subject: Re: Problems with NFS4.1 on ESXi
Date: Sun, 24 Apr 2022 20:39:24 +0000 [thread overview]
Message-ID: <YT2PR01MB97305156E841831C4093CEF4DDF99@YT2PR01MB9730.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <YT2PR01MB9730508253381560F79E96C1DDF99@YT2PR01MB9730.CANPRD01.PROD.OUTLOOK.COM>
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-04-24 20:39 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 [this message]
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
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=YT2PR01MB97305156E841831C4093CEF4DDF99@YT2PR01MB9730.CANPRD01.PROD.OUTLOOK.COM \
--to=rmacklem@uoguelph.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.