Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The ESXi 5.x host gets disconnected from vCenter ServerIt cannot connect the ESXi 5.x host to vCenter ServerIt cannot connect to the ESXi 5.x host using the vSphere ClientThe /var/log/hostd.log file indicates that the host is out of space:VmkCtl Locking (/etc/vmware/esx.conf) : Unable to create or open a LOCK file. Failed with reason: No space left on deviceVmkCtl Locking (/etc/vmware/esx.conf) : Unable to create or open a LOCK file. Failed with reason: No space left on device Running the vdf -h command shows that there is sufficient space in the root file systemThe /var/log/vmkernel.log file indicates that it is out of inodes:cpu4:1969403)WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process python because the visorfs inode table is full.cpu11:1968837)WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process hostd because the visorfs inode table is full.cpu5:1969403)WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process python because the visorfs inode table is full.cpu11:1968837)WARNING: VisorFSObj: 893: Cannot create file /etc/vmware/esx.conf.LOCK for process hostd because the visorfs inode table is full. Running the stat -f / command on ESXi 5.0 indicates that inodes are low Running the localcli system visorfs ramdisk list command on ESXi 5.1 and 5.5 indicates that inodes are low
This issue occurs by the hardware monitoring service (sfcdb) that populates the /var/run/sfcb directory with over 5000 files.
This issue is resolved in: VMware ESXi 5.0 Update 3, available at VMware Downloads. For more information, see the VMware ESXi 5.0 Update 3 Release Notes. VMware ESXi 5.1 Update 2, available at VMware Downloads. For more information, see the VMware ESXi 5.1 Update 2 Release Notes. VMware ESXi 5.5, available at VMware Downloads. For more information, see VMware ESXi 5.5, Patch ESXi550-201312401-BG: Updates esx-base (2063788). To work around this issue, free up inodes. To free up inodes: Note: This process is a temporary workaround. The inodes can reach exhaustion even after adding the RAM disk for the sfcb tickets. Connect to the ESXi host using SSH. Run this command to stop the sfcbd service:/etc/init.d/sfcbd-watchdog stop Manually delete the files in the var/run/sfcb directory to free inodes.Run these commands to remove the files:cd /var/run/sfcbrm [0-2]*rm [3-6]*rm [7-9]*rm [a-c]*rm [d-f]* Run this command to restart the sfcbd service:/etc/init.d/sfcbd-watchdog startNote: Restart management agents after step 4. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490). To prevent root file system from getting impacted on ESXi 5.1 and 5.5: Connect to the ESXi host using SSH. Run this command to stop the sfcbd service:/etc/init.d/sfcbd-watchdog stop Enable this command to be run at boot time:esxcli system visorfs ramdisk add --name sfcbtickets --min-size 0 --max-size 1024 --permissions 0755 --target /var/run/sfcbFor more information, see Modifying the rc.local or local.sh file in ESX/ESXi to execute commands while booting (2043564). Run this command to start the sfcbd service:/etc/init.d/sfcbd-watchdog start Run this command and verify if the new ramdisk exists:esxcli system visorfs ramdisk list Note: This issue may also occur if the SNMP agent is enabled. For more information, see vCenter Server and vmkernel logs report the message: The ramdisk 'root' is full (2033073).
Restarting the Management agents in ESXiESXi/ESX error: No free space left on deviceFreeing ESXi inodesvCenter Server and vmkernel logs report the message: The ramdisk 'root' is fullModifying the rc.local or local.sh file in ESX/ESXi to execute commands while bootingVMware ESXi 5.5, Patch ESXi550-201312401-BG: Updates esx-base sfcbd で inode が枯渇するために ESXi 5.x ホストが vCenter Server から切断される由于 sfcbd 耗尽 inode，因此 ESXi 5.x 主机与 vCenter Server 之间的连接断开