NFS storage inactive but functional

[jbender]

After changing the server address for my backup NFS mount from hostname to IP address, storage volumes are shown in Proxmox UI as enabled but inactive (see screenshot), This includes that no volume usage stats are returned, however, the volumes are fully functional.

My storage.cfg is

nfs: carbon_backup_vms
        export /volume1/proxmox_backup/virtual_machines
        path /mnt/pve/carbon_backup_vms
        server 10.80.29.210
        content backup
        prune-backups keep-all=1

nfs: carbon_backup_nodes
        export /volume1/proxmox_backup/nodes/bc2-nitrogen
        path /mnt/pve/carbon_backup_nodes
        server 10.80.29.210
        content backup
        prune-backups keep-all=1

df -h gives

bc2-carbon.myinternal.network.de:/volume1/proxmox_backup/virtual_machines     15T  5.8T  9.3T  39% /mnt/pve/carbon_backup_vms
bc2-carbon.myinternal.network.de:/volume1/proxmox_backup/nodes/bc2-nitrogen   15T  5.8T  9.3T  39% /mnt/pve/carbon_backup_nodes

I can run backup jobs on the volumes both from the command line and from the UI.
So it seems the mount works as supposed, however, the UI deduces a problem.

Can anyone give me a hint how the storage status is determined internally?

Additional information:

/sbin/showmount --no-headers --exports 10.80.29.210
/volume1/proxmox_backup 10.80.29.197

rpcinfo -p 10.80.29.210
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp    892  mountd
    100005    1   tcp    892  mountd
    100005    2   udp    892  mountd
    100005    2   tcp    892  mountd
    100005    3   udp    892  mountd
    100005    3   tcp    892  mountd
    100024    1   udp    662  status
    100024    1   tcp    662  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp   4045  nlockmgr
    100021    3   udp   4045  nlockmgr
    100021    4   udp   4045  nlockmgr
    100021    1   tcp   4045  nlockmgr
    100021    3   tcp   4045  nlockmgr
    100021    4   tcp   4045  nlockmgr

 

[oicfar]

I had same problem with my NFS mount from Synology in Proxmox. After I set


(3 works too) the NFS mount is shown as active and I see the qota.

 

[jbender]

Not sure if I explicitly provided the NFS version (it was v3 in my case) in Proxmox, that's a good point.

In the meantime I switched to using a containerized Proxmox backup server on Synology (https://hub.docker.com/r/ayufan/proxmox-backup-server) which worked very well so far. However, I removed the NFS share and hence cannot comment if changing the NFS parameter would have fixed it for my case.