Hi Forum, Thread small update in case anyone else hits this topic. I just bumped into this / came here via google search.
Context in my case:
- 3 node proxmox with mostly local storage 'share nothing' storage pools
- one NFS storage pool existed
- due to maintenance issues with hosting provider, the NFS storage pool server had to move to a new IP address. So NFS config needed adjust.
- I disabled the NFS storage pool in proxmox (ie, GUI > storage > NFS thing > Un-ticked the "enabled" box)
- then service provider migrated my NFS server, and gave it NEW IP address and then I tried to re-establish it as functional NFS storage in Proxmox.
- it seems no way to change an IP of an NFS storage in proxmox, so the path is to delete and re-create (I think).
the drama was that once I deleted the NFS storage pool config in proxmox. I was not able to add it back in with the new IP. giving me a timeout.
looking on the CLI, the output from 'mount' command still showed me the old mount was present
and output of "Dmesg" command tells me clearly lots of NFS TIMEOUT grumpy errors. For the no-longer-existing IP address of the NFS storage I tried to disable/remove.
note I have nothing in /etc/fstab related to this NFS mount. It was managed purely via GUI / proxmox storage UI.
Next step I tried to do a 'force' unmount and that tells me simply "Nope, device is busy, get bent!".
as per
umount -f /mnt/pve/nfs-misc
Then Finally I tried a "LAZY" unmount, and it seems the soft touch approach is better here.
umount -l /mnt/pve/nfs-misc
did not return any error, the NFS mount no longer is shown in output of "mount" command
and now bingo happy days I am proceed with adding the NFS storage back in / with the same name as before / but with a new IP address for the NFS server. And things 'just work fine'.
and of course I had to do the lazy-unmount thing on all 3 notes of proxmox cluster to make them all equally happy with the situation.
hope this info maybe of help to someone / or even just me in the future if I forget the solution and find it again via google in a year or two
Tim