From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [RFC PATCH storage 0/2] nfs: use rpcinfo as a showmounts fallback for nfs3
Date: Wed, 4 Mar 2026 16:45:47 +0100 [thread overview]
Message-ID: <20260304154551.503663-1-m.sandoval@proxmox.com> (raw)
See the respective commit messages.
This came up in enterprise support in which the showmounts command failed but
rpcbind succeeded (with -T tcp).
This possibility was discussed with Friedrich and Fiona off-list. I hope to get
more feedback here.
This is not yet tested as I need to find a reproducer for a few cases. I Will
update once this is tested.
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-04 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:45 Maximiliano Sandoval [this message]
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 ` [RFC PATCH storage 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=20260304154551.503663-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox