From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [RFC PATCH storage 2/2] nfs: use rpcinfo as a showmounts fallback for nfs3
Date: Wed, 4 Mar 2026 16:45:49 +0100 [thread overview]
Message-ID: <20260304154551.503663-3-m.sandoval@proxmox.com> (raw)
In-Reply-To: <20260304154551.503663-1-m.sandoval@proxmox.com>
The check_connection call must succeed in order for the NFS storage to
be activated. In a setup in which the NFS server does not list exports
and which only supports NFSv3 this would result in the storage not being
usable (not without manually mounting the NFS share and using the
Directory storage instead). We add a fallback check with rpcinfo for
this case.
The rpcinfo check was replaced with showmounts in f8b0d82fe. At the time
the rationale was that rpcinfo did not have support for ipv6
connections, which is not the case at the moment.
In order to not break compatibility with setups that already activate
correctly, we add a rpcinfo check as a fallback for NFSv3-only setups
only after the showmounts command fails.
Potential pitfalls:
- Some NFSv3 servers might only support UDP [RFC 1813]
- The two timeouts add up to 20 seconds which might be too much
- Some NFS servers might not have rpcbind as described in acff89540
[RFC 1813]: https://datatracker.ietf.org/doc/html/rfc1813#section-2.3
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
src/PVE/Storage/NFSPlugin.pm | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/PVE/Storage/NFSPlugin.pm b/src/PVE/Storage/NFSPlugin.pm
index 062b3f32..3654e8b3 100644
--- a/src/PVE/Storage/NFSPlugin.pm
+++ b/src/PVE/Storage/NFSPlugin.pm
@@ -193,10 +193,12 @@ sub check_connection {
my $cmd;
+ my $is_v3 = defined($opts) && $opts =~ /vers=3.*/;
my $is_v4 = defined($opts) && $opts =~ /vers=4.*/;
if ($is_v4) {
$cmd = tcp_rpcinfo_cmd($server, '4');
} else {
+ # TODO Consider switching to rpcinfo altogether for Proxmox VE 10.
$cmd = ['/sbin/showmount', '--no-headers', '--exports', $server];
}
@@ -213,6 +215,12 @@ sub check_connection {
return 0 if $port == 0;
return PVE::Network::tcp_ping($server, $port, 2);
+ } elsif ($is_v3) {
+ $cmd = tcp_rpcinfo($server, '3');
+ eval {
+ run_command($cmd, timeout => 10, outfunc => sub { }, errfunc => sub { });
+ };
+ return 1 if !$@;
}
return 0;
}
--
2.47.3
prev parent reply other threads:[~2026-03-04 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:45 [RFC PATCH storage 0/2] " Maximiliano Sandoval
2026-03-04 15:45 ` [RFC PATCH storage 1/2] nfs: create a helper to run rpcinfo commands Maximiliano Sandoval
2026-03-04 15:45 ` Maximiliano Sandoval [this message]
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=20260304154551.503663-3-m.sandoval@proxmox.com \
--to=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.