\nIssue affects ESXi 5.5 and ESXi 6.x running HPE CIM providers, such as OEM HPE customized images.<\/p>\n
Symtomps<\/strong> Below you will find workarounds to address this issue. 1. Disable HA on the cluster to avoid alerts. Permanent workaround<\/strong><\/p>\n Now to address this issue permanently i suggest implementing cron job, which clears files every hour from \/var\/run\/sfcb directory. Make sure to clear all files prior using instructions above prior to proceeding with this. Now onto our permanent solution – SSH into the host and edit That’s it.<\/p>\n","protected":false},"excerpt":{"rendered":" Another bug from VMware\/HPE – unfortunately we don’t have public KB available at this point. As per our conversation with VMware engineer this issue affects both ESXi 5.5 and ESXi 6.x hosts. I suspect VMware sfcb service fails to clear … Continue reading
\nUnable to power on new VMs, vMotion fails.
\nvkernel.log shows the following errors:
\nCannot create file \/var\/run\/sfcb\/52494bef-1566-c7e5-6604-676ddd5b9c46 for process sfcb-CIMXML-Pro because the inode table of its ramdisk (root) is full.
\n<\/code>
\nYou see alot of files inside \/var\/run\/sfcb directory
\n![\"sfcb_2\"](\"https:\/\/blog.gptnet.net\/wp-content\/uploads\/2016\/08\/sfcb_2.png\")
<\/a>
\n![\"sfcb_4\"](\"https:\/\/blog.gptnet.net\/wp-content\/uploads\/2016\/08\/sfcb_4.png\")
<\/a><\/p>\n
\n
\nTemporary workaround<\/strong><\/p>\n
\n2. Stop SFCB by running the following command:
\n\/etc\/init.d\/sfcbd-watchdog stop<\/code>
\n3. Delete files inside \/var\/run\/sfcb
\nIf you get error -sh: can't fork<\/code> delete files in small batches with commands such as rm [0-2]*<\/code> or even more granual with rm abcd*<\/code>
\n![\"sfcb_3\"](\"https:\/\/blog.gptnet.net\/wp-content\/uploads\/2016\/08\/sfcb_3.png\")
<\/a>
\n4. Start SFCB by running the following command:
\n\/etc\/init.d\/sfcbd-watchdog start<\/code>
\n5. Verify fs for free ionodes:
\nesxcli system visorfs ramdisk list<\/code>
\n6. Restart management agents
\n\/etc\/init.d\/hostd restart
\n\/etc\/init.d\/vpxa restart<\/code>
\nAt this point host will temporary disconnect from vCenter, so don’t panic as all VMs are still online.<\/p>\nvi \/etc\/rc.local.d\/local.sh<\/code> file. Copy and paste the following above exit 0<\/code>
\n#custom workaround by Naz Snidanko nsnidanko@act.bm 7\/26\/2016 to address vmware bug
\n#1. Stop cron service
\n\/bin\/kill $(cat \/var\/run\/crond.pid)
\n#2. Instert new crontab entry
\n\/bin\/echo \"0 * * * * for i in \/var\/run\/sfcb\/*; do rm -rf \\$i; done\" >> \/var\/spool\/cron\/crontabs\/root
\n#3. Start cron service
\n\/usr\/lib\/vmware\/busybox\/bin\/busybox crond<\/code><\/p>\n![\"sfcb_1\"](\"http:\/\/blog.gptnet.net\/wp-content\/uploads\/2016\/08\/sfcb_1.png\")
<\/a><\/p>\n