Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

Freeing ESXi inodes (1008643)


ESXi hosts that exhibit these symptoms may have low inodes:
  • The ESXi host disconnects from vCenter Server
  • The script does not restart services
  • The output of stat -f / indicates that inodes are low
  • The host management agent, the hostd process becomes unresponsive
  • The esxcfg-swiscsi -q command (or any command that interacts with esx.conf, such as esxcfg-info) produces errors similar to:

    • Error interacting with configuration file /etc/vmware/esx.conf: Write failed during Unlock.This is likely due to a full or read-only filesystem

    • Error interacting with configuration file /etc/vmware/esx.conf:
      Unable to write to file /etc/vmware/esx.conf.bXQvyt while saving /etc/vmware/esx.conf operation aborted.

    • Unlock of ConfigFileLocker failed : Error interacting with configuration file /etc/vmware/esx.conf

  • On the summary page for a host, you see a message similar to:

    Unable to apply DRS resource settings on host in <ClusterName>. A general system error occurred: vmodl.fault.SystemError. This can significantly reduce the effectiveness of DRS.


If an ESXi host has low inodes, you may have to free inodes on the host.

To verify that a host has low inodes, run the command:

[root@esxhost root]# stat -f /

The output appears similar to:

File: "/"
    ID: 0        Namelen: 255     Type: ext2/ext3
Blocks: Total: 1290707    Free: 718116     Available: 652551     Size: 4096
Inodes: Total: 656000     Free: 0

Note: The Free: field refers to the number of available free inodes. If it is zero (or close to 0), the amount of free inodes is insufficient.

To free inodes on an ESXi host:
  1. On the ESXi host, enter Tech Support Mode. For more information, see Tech Support Mode for Emergency Support (1003677).
  2. Delete the /var/log/vmware/aam/rule directory.
  3. Delete any files in the /var/core/ directory.
  4. Uninstall the vpxa and aam clients with the uninstall scripts in /opt/vmware/uninstallers ( and, respectively).
  5. Restart ESXi services with the /sbin/ script.
  6. Reconnect the ESXi host to VirtualCenter.
  7. Investigate for the recent presence of more than usual small files, such as files ending .txt or .dmp. If they are present, delete the files, then check the inodes.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 2 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 2 Ratings