all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH storage v4 2/2] nfs: use rpcinfo as a showmount fallback for nfs3
Date: Tue, 7 Jul 2026 10:06:43 +0200	[thread overview]
Message-ID: <efe8df03-3148-4516-8a4a-ff681aea80e7@proxmox.com> (raw)
In-Reply-To: <s8o7bn7p7w2.fsf@toolbox>

Am 07.07.26 um 9:37 AM schrieb Maximiliano Sandoval:
> Fiona Ebner <f.ebner@proxmox.com> writes:
> 
>> Am 06.07.26 um 4:37 PM schrieb Maximiliano Sandoval:
>>> diff --git a/src/PVE/Storage/NFSPlugin.pm b/src/PVE/Storage/NFSPlugin.pm
>>> index 56dbd9ec..4fe7695a 100644
>>> --- a/src/PVE/Storage/NFSPlugin.pm
>>> +++ b/src/PVE/Storage/NFSPlugin.pm
>>> @@ -198,6 +198,11 @@ sub check_connection {
>>>          # no exports are listed
>>>          $cmd = $nfs_get_rpcinfo_command->($server, '4');
>>>      } else {
>>> +        # FIXME: PVE 10: Consider switching to rpcinfo altogether.
>>> +        # There are some potential pitfalls:
>>> +        # - Some NFSv3 servers might only support UDP (cf. RFC 1813, Section 2.3)
>>> +        # - The two timeouts add up to a potential worst-case scenario of 20 seconds
>>
>> This is not a pitfall for to the switch to rpcinfo, but related to your
>> current implementation with showmount+rpcinfo. It's rather easy to spot,
>> so not sure it needs a comment in the code. I'd rather have it in the
>> commit message.
> 
> Running into timeouts is a very common issue in Enterprise support, I do
> have a strong preference for keeping it as explicit as possible.

But please don't mention it in the pitfalls for the switch to rpcbind,
but clearly state that it's about the current implementation. Otherwise,
that is just confusing.




  reply	other threads:[~2026-07-07  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 14:36 [PATCH storage v4 0/2] nfs: use rpcinfo as a showmount fallback for nfs3 Maximiliano Sandoval
2026-07-06 14:36 ` [PATCH storage v4 1/2] nfs: create a helper to get rpcinfo commands Maximiliano Sandoval
2026-07-06 14:36 ` [PATCH storage v4 2/2] nfs: use rpcinfo as a showmount fallback for nfs3 Maximiliano Sandoval
2026-07-07  7:07   ` Fiona Ebner
2026-07-07  7:37     ` Maximiliano Sandoval
2026-07-07  8:06       ` Fiona Ebner [this message]
2026-07-07  8:24         ` superseded: " Maximiliano Sandoval

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=efe8df03-3148-4516-8a4a-ff681aea80e7@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal