Hello,
We have been having problems with our daily vzdumps to our NFS storage. We are getting "ASK ERROR: could not activate storage 'backups': storage 'backups' is not online".
We utilize an external Ceph Quincy cluster with the ganesha.nfs daemon, and have no problems with the storage. It mounts, and IOPS/connection are solid when it's mounted on any host we have tested. Quincy does utilize NFS without an rpcbind service in 4+, and the code checks to see if rpcbind responds in the "NFSPlugin.pm" codebase within the function check_connection.
We bypass'd this by commenting out the eval, and we had no problems when viewing the storage within the GUI. However, we still get the issue when the daily vzdumps which is most likely related to the sub activate_storage.
I have traced the function to nfs_is_mounted which I believe is the source, and nfs_is_mounted does find the correct mount point when it does a grep on the array. Has any encountered this issue with Proxmox, or have a work around?
Thanks,
Scott Ehas
We have been having problems with our daily vzdumps to our NFS storage. We are getting "ASK ERROR: could not activate storage 'backups': storage 'backups' is not online".
We utilize an external Ceph Quincy cluster with the ganesha.nfs daemon, and have no problems with the storage. It mounts, and IOPS/connection are solid when it's mounted on any host we have tested. Quincy does utilize NFS without an rpcbind service in 4+, and the code checks to see if rpcbind responds in the "NFSPlugin.pm" codebase within the function check_connection.
We bypass'd this by commenting out the eval, and we had no problems when viewing the storage within the GUI. However, we still get the issue when the daily vzdumps which is most likely related to the sub activate_storage.
I have traced the function to nfs_is_mounted which I believe is the source, and nfs_is_mounted does find the correct mount point when it does a grep on the array. Has any encountered this issue with Proxmox, or have a work around?
Thanks,
Scott Ehas