I've just been notified about annoying problem by customer for whom I did vSphere 5.5 Design. The datastore was not posible to unmount. In ESX logs were something similar to message below.
The solution is to disable vsantraced service so it is necessary to issue following command on evey ESX ...
Not so nice, right? That's the downside of fully integrated VSAN software into general ESX hypervisor. I'm not happy with this approach. In my opinion, it would be much better distribute VSAN as additional software installing as regular VIB (VMware Installable Bundle).
Cannot unmount volume 'Datastore Name: vm3:xxx VMFS uuid: 517c9950-10f30962-931f-00304830a1ea' because file system is busy. Correct the problem and retry the operation.There is KB about this symptom. VSAN component VSANTRACE was using datastore. That was the reason of busy file system. It was pretty annoying issue as VSAN was not used nor enabled.
The solution is to disable vsantraced service so it is necessary to issue following command on evey ESX ...
chkconfig vsantraced off
Not so nice, right? That's the downside of fully integrated VSAN software into general ESX hypervisor. I'm not happy with this approach. In my opinion, it would be much better distribute VSAN as additional software installing as regular VIB (VMware Installable Bundle).
3 comments:
Hi David,
Have you found a way to automate disabling this service?
I am also internal Dell and struggling with the same issue.
Not really as we had just 16 node vSphere cluster we did manual ssh to every host and disabled vsantraced service. SSH task can be automated but it depends how many ESXi hosts do you have and what is faster. Develop and test the script or do it manually?
Yep, that is what we're struggling with too. It doesn't look like powercli can help automate this, we'd have to do something with SSH and plink. Will follow up here if I go any further with this.
Would love to chat some time about what you're doing within Dell!
Post a Comment