jtp755

I have not found a solution other than disabling cache on the pool in order to get the storage stable and usable in Proxmox host (not specific VMs or LXCs) - just adding it as storage.

So the other share you have mounted in the Ubuntu VM - the VM is running on Proxmox? Im betting that would work as its using the OS which is good news. I am going to change mine tomorrow to have cache enabled but mount the NFS via /etc/fstab and see how that goes. Didnt get to it today.

I have been running for 24hrs with cache turned off on my backup share in Unraid and it has not even blipped in Proxmox. All snapshots have written fine and I can still browse the attached storage from Proxmox. Seems to definitely be something with cache-enabled. I did see quite a few posts yesterday when I was looking in to it add the NFS share in /etc/fstab for automount and then in Proxmox use local filesystem to add the storage. I have not tried this yet though.

I am having this issue with NFS and digging in to it as well. Ill give the no cache drive a try and see if anything changes. What I find odd in my case is that I can add the NFS share to my cluster, see it on both nodes, set up a backup job, run said backup job and everything works great. Leave it for a bit and come back and the storage on both nodes has a question mark and inaccessible. I have another NFS share mounted from another NAS and that has been solid.