From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH storage v2 0/2] nfs: use rpcinfo as a showmounts fallback for nfs3
Date: Thu, 19 Mar 2026 11:42:30 +0100 [thread overview]
Message-ID: <20260319104241.191910-1-m.sandoval@proxmox.com> (raw)
See the respective commit messages.
This came up in enterprise support. In this case the NFS appliance only
supported NFSv3 and the showmounts command failed, but rpcbind
succeeded (with -T tcp).
This possibility was discussed with Friedrich and Fiona off-list.
Tested:
- Created a NFS share on host "B"
- On host "A" a NFS storage was added (using B's share) with --options vers=3
- Ran `ss -tulpn4 |grep mountd` on host B to see ports used by showmounts
- The ports listed were blocked on host "A", so that showmount fails:
/sbin/showmount --no-headers --exports $B
rpc mount export: RPC: Unable to send; errno = Operation not permitted
- Ran `pvesm status` on A and checked that the NFS storage is available
- Created a VM on A with a disk image in the the NFS storage
The later two operations would have failed without the changes here.
Differences from v1:
- the name of the helper function was fixed
Maximiliano Sandoval (2):
nfs: create a helper to run rpcinfo commands
nfs: use rpcinfo as a showmounts fallback for nfs3
src/PVE/Storage/NFSPlugin.pm | 33 +++++++++++++++++++++++----------
1 file changed, 23 insertions(+), 10 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-19 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 10:42 Maximiliano Sandoval [this message]
2026-03-19 10:42 ` [PATCH storage v2 1/2] nfs: create a helper to run rpcinfo commands Maximiliano Sandoval
2026-03-19 10:42 ` [PATCH storage v2 2/2] nfs: use rpcinfo as a showmounts fallback for nfs3 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=20260319104241.191910-1-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.