Deletion of an NFS datastore generates the following error:
Sysinfo error on operation returned the following status: Busy
Which step can be performed that will allow the deletion to complete successfully?
A.
Storage vMotion any virtual machines on the datastore to another location.
B.
Remove the datastore from the Storage DRS cluster in which it resides.
C.
Verify the value of the NFS.HeartbeatDelta is not set to 0.
D.
Suspend any running virtual machines and unmount the NFS datstore.
Explanation:
Explanation/Reference:
D is correct
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.storage.doc/GUID-1B56EF97-F60E-4F21-82A7-8F2A7294604D.html
0
0
Actually, A is correct.
When appropriate, before unmounting datastores, make sure that the following prerequisites are met:
– No virtual machines reside on the datastore.
– The datastore is not managed by Storage DRS.
– Storage I/O control is disabled for this datastore.
https://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vsphere.storage.doc/GUID-1B56EF97-F60E-4F21-82A7-8F2A7294604D.html
Before unmounting a LUN, ensure that:
– If the LUN is being used as a VMFS datastore, all objects (such as virtual machines, snapshots, and templates) stored on the VMFS datastore are unregistered or moved to another datastore.
– The datastore is not used for vSphere HA heartbeat.
– The datastore is not part of a datastore cluster.
– The datastore is not managed by Storage DRS.
– The datastore is not configured as a diagnostic coredump partition.
– Storage I/O Control is disabled for the datastore
– No third-party scripts or utilities running on the ESXi host can access the LUN that has issue. If the LUN is being used as a datastore, unregister all objects (such as virtual machines and templates) stored on the datastore.
– If the LUN is being used as an RDM, remove the RDM from the virtual machine. Click Edit Settings, highlight the RDM hard disk, and click Remove. Select Delete from disk if it is not selected and click OK.
– Check if the LUN/datastore is used as the persistent scratch location for the host.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004605
0
0
For me it’s B
0
0
The reason it is A and not B is because of the error being thrown. The error indicates file locks exist. The NFS datastore would also need to be removed from an SDRS Cluster prior to being deleted but if this were the problem then we’d be seeing a different error message.
0
0
From the options provided, A is correct.
http://www.mindthevirt.com/unmount-vmware-datastore-device-busy-399
0
0