From: "J. Bruce Fields" <bfields@fieldses.org>
To: Daire Byrne <daire@dneg.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: nconnect & repeating BIND_CONN_TO_SESSION?
Date: Mon, 10 Jan 2022 09:52:10 -0500 [thread overview]
Message-ID: <20220110145210.GA18213@fieldses.org> (raw)
In-Reply-To: <CAPt2mGPtxNzigMEYXKFX0ayVc__gyJcQJVHU51CKqU+ujqh7Cg@mail.gmail.com>
On Mon, Jan 10, 2022 at 09:21:44AM +0000, Daire Byrne wrote:
> On Fri, 7 Jan 2022 at 17:17, J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> > Hm, doesn't each of these use up a reserved port on the client by
> > default? I forget the details of that. Does "noresvport" help?
>
> Yes, I think this might be the issue. It seems like only 13/16
> connections actually initially get setup at mount time and then it
> tries to connect the full 16 once some activity to the mountpoint
> starts. My guess is that we run out of reserved ports at that point
> and continually trigger the BIND_CONN_TO_SESSION.
>
> I can use noresvport with an NFSv3 client mount and it seems to do the
> right thing (with the server exporting "insecure), but it doesn't seem
> to have any effect on a NFSv4.2 mount (still uses ports <1024). Is
> that expected?
No. Sounds like something's going wrong.
--b.
> Perhaps NFSv4.2 doesn't allow "insecure" mounts?
>
> Daire
next prev parent reply other threads:[~2022-01-10 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 12:26 nconnect & repeating BIND_CONN_TO_SESSION? Daire Byrne
2022-01-07 17:17 ` J. Bruce Fields
2022-01-07 17:59 ` Rick Macklem
2022-01-07 18:56 ` J. Bruce Fields
2022-01-07 19:15 ` pynfs regression with nfs4.1 RNM18, RNM19 and RNM20 with ext4 dai.ngo
2022-01-07 19:41 ` Chuck Lever III
2022-01-07 20:01 ` dai.ngo
2022-01-10 9:21 ` nconnect & repeating BIND_CONN_TO_SESSION? Daire Byrne
2022-01-10 14:52 ` J. Bruce Fields [this message]
2022-01-10 17:21 ` J. Bruce Fields
2022-01-23 21:56 ` Daire Byrne
2022-01-23 22:42 ` J. Bruce Fields
2022-01-24 12:33 ` Daire Byrne
2022-02-07 15:21 ` Daire Byrne
2022-02-07 15:53 ` J. Bruce Fields
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=20220110145210.GA18213@fieldses.org \
--to=bfields@fieldses.org \
--cc=daire@dneg.com \
--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.