NFS share not correctly unmounted

[lamera]

Hi together

I tried to configure a new NFS share on my Proxmox Cluster. I made a mistake and deleted the working NFS share from the GUI.
After the storage change I tried to remount the NFS share from the GUI with the same name. I keep getting this error:

NFS Shares: storage is not online (500)

I searched the web for a workaround. Then I had a look at /mnt/pve/ with ls and I saw this:

d????????? ? ?      ?             ?             ? Backups

I tried to delete this empty folder but the ressource/device is "busy".

It seems to me that Proxmox doesn't terminate the connection properly?
Maybe I found a solution with rebooting all nodes and removing this empty folder in /mnt/pve/.
Any inputs?

 

[fiona]

Hi,
for hanging NFS mounts, I've seen umount -f -l /mnt/pve/Backups recommended. See man umount for more information about the flags.

 

[lamera]

Hi,
for hanging NFS mounts, I've seen umount -f -l /mnt/pve/Backups recommended. See man umount for more information about the flags.

Hi @Fabian_E

I can confirm my solution with rebooting worked fine. I assume your solution would also work.
But I think there is an issue in Proxmox that doesn‘t correctly unmount the shares. Can you reproduce the behaviour?

 

[fiona]

Deleting the NFS from Proxmox VE's storage configuration does only delete it from the configuration. This is true for all storages and is by design. After all, something might still be using the mount. Proxmox VE will detect when a network mount is hanging/unavailable, but fixing that is not really something that can be done automatically.