2V0-621D · Question #139
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…
The correct answer is A. Storage vMotion any virtual machines on the datastore to another location. A "Busy" error during NFS datastore deletion typically means resources like virtual machines are still residing on or actively using the datastore. Moving all virtual machines off the datastore will resolve this conflict and allow deletion.
Question
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?
Options
- AStorage vMotion any virtual machines on the datastore to another location.
- BRemove the datastore from the Storage DRS cluster in which it resides.
- CVerify the value of the NFS.HeartbeatDelta is not set to 0.
- DSuspend any running virtual machines and unmount the NFS datstore.
How the community answered
(52 responses)- A81% (42)
- B6% (3)
- C12% (6)
- D2% (1)
Why each option
A "Busy" error during NFS datastore deletion typically means resources like virtual machines are still residing on or actively using the datastore. Moving all virtual machines off the datastore will resolve this conflict and allow deletion.
The "Busy" error indicates that the NFS datastore is actively being used, most commonly by virtual machines or their files still residing on it. Storage vMotion migrates all virtual machine files and disks to another datastore, effectively vacating the original NFS datastore and allowing its successful deletion.
Removing a datastore from a Storage DRS cluster does not free up the datastore from virtual machines actively using it, which is the direct cause of a "Busy" error during deletion.
The NFS.HeartbeatDelta setting relates to the NFS client's heartbeat mechanism for monitoring server availability, not to whether a datastore is actively used by virtual machines preventing its deletion.
Suspending virtual machines keeps their files on the datastore, thus it remains "busy"; unmounting is typically attempted after ensuring no active usage, and will fail if the datastore is still busy.
Concept tested: Resolving datastore busy errors before deletion
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-8D4C811D-4573-45B1-9B3B-86469C311096.html
Topics
Community Discussion
No community discussion yet for this question.