acff89540a
by simply doing a ping with the expected port as a fallback when the rpcinfo command fails. The timeout was chosen to be 2 seconds, because that's what the existing callers of tcp_ping() in the iSCSI and GlusterFS plugins use. Alternatively, the existing check could be replaced, but that would 1. Dumb down the check. 2. Risk breakage in some corner case that's yet to be discovered. 3. It would still be necessary to use rpcinfo (or dumb the check down even further) in case port=0; from 'man 5 nfs' about the NFSv4 'port' option: > If the specified port value is 0, then the NFS client uses the NFS > service port number advertised by the server's rpcbind service. Reported in the community forum: https://forum.proxmox.com/threads/118466/post-524449 https://forum.proxmox.com/threads/120774/ Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>