Welcome back, I hope everyone had some time to relax and spend the christmas holidays with their families. I was lucky enough to have some time off and play with my lab.
After playing around with some newly deployed NFS datastores, I tried to unmount them and I got a device busy error and on the CLI I’ve got Sysinfo error on operation returned status : Busy. Please see the VMkernel log for detailed error information.
Let me show you the steps I ran through:
- Mounted a newNFSdatastore throughtheESXCLI
-
esxcli storage nfs add --host=nas-ip --share=share-name --volume-name=volume_name
-
- List all NFS shares
-
~ # esxcli storage nfs list
-
- Verify that all VMs on this datastore are either powered off or have been vMotioned to another datastore
- Trytounmountthedatastore
-
esxcli storage nfs remove -v b3c1 Sysinfo error on operation returned status : Busy. Please see the VMkernel log for detailed error information
-
- Looking through the vmkernel.log, doesn’thelpmuch either. The only messageprintedthere is
-
2015-01-12T23:10:09.357Z cpu2:49350 opID=abdf676b)WARNING: NFS: 1921: b3c1 has open files, cannot be unmounted
-
- After some searching, I found this article on VMware
- Basically, the issue seems to be that vSphere HA Datastore Heartbeats are enabled on this datastore, which is causing the device to be busy.
The solution for this problem is pretty simple. Open your vSphere Client and edit the vSphere HA settings, after selecting your vSphere HA Cluster. Within the settings, make sure to set the vSphere HA heartbeats to Use Datastores only from the specified list and deselect your datastore, which you try to unmount.
After changing the setting, I was able to successfully unmount the NFS share with the following command esxcli storage nfs remove -v datastore_name