Host losing NFS datastore when renamed existing NFS and presented new Share with the old name of an existing share
book
Article ID: 328651
calendar_today
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
When we rename NFS while mapping an NFS share to a host, if the new name conflicts with the older name we receive error,
Host loses the access to the existing NFS share. Symlink for the NFS share becomes invalid.
Cause
This issue is caused when there is a clash between existing and new NFS device name.
Resolution
This issue is resolved in VMware vSphere ESXi 6.5 P03, available at Broadcom Downloads. This issue is resolved in VMware vSphere ESXi 6.7, available at Broadcom Downloads.
Workaround: Reboot the hosts where the NFS shares are present.
Additional Information
Impact/Risks: Host loses the access to the existing NFS share with share path /nas/nfs-0, which was renamed as NFS-0-renamed.