From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH storage v3 0/2] nfs: use rpcinfo as a showmounts fallback for nfs3
Date: Mon, 06 Jul 2026 16:38:19 +0200 [thread overview]
Message-ID: <s8o4iic6v50.fsf@toolbox> (raw)
In-Reply-To: <20260325124646.298999-1-m.sandoval@proxmox.com> (Maximiliano Sandoval's message of "Wed, 25 Mar 2026 13:46:43 +0100")
Maximiliano Sandoval <m.sandoval@proxmox.com> writes:
> 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.
Superseded-by: https://lore.proxmox.com/all/20260706143638.509139-1-m.sandoval@proxmox.com/T/#u
--
Maximiliano
prev parent reply other threads:[~2026-07-06 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:46 [PATCH storage v3 0/2] nfs: use rpcinfo as a showmounts fallback for nfs3 Maximiliano Sandoval
2026-03-25 12:46 ` [PATCH storage v3 1/2] nfs: create a helper to run rpcinfo commands Maximiliano Sandoval
2026-07-06 13:01 ` Fiona Ebner
2026-03-25 12:46 ` [PATCH storage v3 2/2] nfs: use rpcinfo as a showmounts fallback for nfs3 Maximiliano Sandoval
2026-07-06 13:01 ` Fiona Ebner
2026-07-06 14:19 ` Maximiliano Sandoval
2026-07-06 14:38 ` 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=s8o4iic6v50.fsf@toolbox \
--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