Was setting up a NFS volume in openfiler for a lab and hit this strange error on the ESXi host:
2014-09-25T18:36:53.522Z cpu11:32806)WARNING: NFS: 316: Lost connection to the server 10.1.1.51 mount point /mnt/data01/vol01/Openfiler01/, mounted as 05730b90-cf23e830-0000-000000000000 ("Openfiler01") 2014-09-25T18:36:54.524Z cpu10:216948)WARNING: NFS: 2144: Failed to get attributes (I/O error) 2014-09-25T18:36:54.524Z cpu10:216948)NFS: 2207: Failed to get object 36 5730b90 cf23e830 70001 8000080 0 dc16020f c9496472 871a149a 2fb062cb 0 0 0 :I/O error On the ESXi host, i was able to mount the volume successfully and everytime i tried accessing files on the volume, it would go inactive and I had to remove and mount the nfs volume again....
Caution: The following steps will cause data loss.
Two ways to completely delete a VSAN datastore:
I. Move the hosts outside the cluster and delete the cluster
Remove all the disk groups configured on the host Put the host into maintenance mode. Move the host outside the cluster Delete the cluster II. Through esxcli
Remove all the disk groups configured on the host Open an SSH session to each of the esxi hosts that are part of the vsan cluster Run the command, “esxcli vsan cluster leave”
VOD or VPX operational dashboard was introduced in vCenter Server 2.0.1 as a debugging/troubleshooting tool integrated with vCenter Server. It displays a dashboard of the Virtual Center runtime state and some internal statistics. This was not publicly announced but was used by VMware personnel for troubleshooting. It still exists today in the vCenter Server 5.5.
VOD also saves all of the runtime statistics periodically into the vpxd-profiler.log or profiler.log and is enabled by default....
VMware DPM(Distributed Power Management) is a feature that is enabled at a cluster level(part of DRS) in vCenter Server. VMware DPM helps to reduce power consumption by powering off hosts where CPU/Memory demand(Virtual Machine CPU/Memory actual usage + unsatisfied demand) is low. How does VMware DPM decide when to power off or power on an ESXi host in the cluster?
VMware DPM calculates the CPU/Memory demand at the cluster level(from all the ESXi hosts in the cluster)....
As per https://communities.vmware.com/docs/DOC-9279
%USED is the percentage of physical CPU time accounted to the world. If a system service runs on behalf of this world, the time spent by that service (i.e. %SYS) should be charged to this world. If not, the time spent (i.e. %OVRLP) should not be charged against this world.
So ideally, %USED = %RUN + %SYS - %OVRLP
However, why does this value exceed 100%?
The answer simply is Turbo boost....