Articles > Virtualization
Errors I was receiving:
No space left on device
a general system error occurred: failed to create journal file provider: failed to open /var/log/vmware/journal/1356997206.7 for write: There is no space left on the device
Unable to connect to the MKS: a general system error occurred: internal error
also, a touch command would not work on the local data store anywhere except in the /tmp folder. It did work on all VMFS volumes, but not the local data store.
I could not open the console for any VM on this host and vMotion would not work.
2013-01-01T00:54:44.538Z [725D0B90 info 'ha-eventmgr'] Event 15908 : The file table of the ramdisk 'root' is full. As a result, the file /var/run/vmware/tickets/vmtck-94dbc1f4-bdcc-43 could not be created by the application 'ticket'.
2012-12-29T12:37:28.196Z cpu20:174084)WARNING: VisorFSObj: 1954: Cannot create file /var/run/vmware/tickets/vmtck-52d47c67-5ca6-8c for process hostd-worker because the inode table of its ramdisk (root) is full.
This article did not help. There was not a free space or inodes issue:
VMware KB: ESX error: No free space left on device
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1007638&sliceId=2&docTypeID=DT_KB_1_1&dialogID=595766083&stateId=1%200%20595772201
Resolution:
I rebooted the host, the problem was gone. I then began to install all patches. Update 2 for vSphere 5.1 was available.
after updating host I was on build 914609 before updating host I was at 838463
this article describes some of my problems, except my ram disk is only 1% full according to "df -h"
VMware KB: Creating a persistent scratch location for ESXi 4.x and 5.x
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696
VMware KB: ESX error: No free space left on device
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1007638&sliceId=2&docTypeID=DT_KB_1_1&dialogID=595766083&stateId=1%200%20595772201
KNOWN ISSUE!!!
VMware KB: ESXi 5.1 host becomes unresponsive when attempting a vMotion or a configuration change
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2040707
vSphere 5.1 update 1 - no space left on device
Last Updated: 1/2/13Errors I was receiving:
No space left on device
a general system error occurred: failed to create journal file provider: failed to open /var/log/vmware/journal/1356997206.7 for write: There is no space left on the device
Unable to connect to the MKS: a general system error occurred: internal error
also, a touch command would not work on the local data store anywhere except in the /tmp folder. It did work on all VMFS volumes, but not the local data store.
I could not open the console for any VM on this host and vMotion would not work.
2013-01-01T00:54:44.538Z [725D0B90 info 'ha-eventmgr'] Event 15908 : The file table of the ramdisk 'root' is full. As a result, the file /var/run/vmware/tickets/vmtck-94dbc1f4-bdcc-43 could not be created by the application 'ticket'.
2012-12-29T12:37:28.196Z cpu20:174084)WARNING: VisorFSObj: 1954: Cannot create file /var/run/vmware/tickets/vmtck-52d47c67-5ca6-8c for process hostd-worker because the inode table of its ramdisk (root) is full.
This article did not help. There was not a free space or inodes issue:
VMware KB: ESX error: No free space left on device
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1007638&sliceId=2&docTypeID=DT_KB_1_1&dialogID=595766083&stateId=1%200%20595772201
Resolution:
I rebooted the host, the problem was gone. I then began to install all patches. Update 2 for vSphere 5.1 was available.
after updating host I was on build 914609 before updating host I was at 838463
this article describes some of my problems, except my ram disk is only 1% full according to "df -h"
VMware KB: Creating a persistent scratch location for ESXi 4.x and 5.x
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696
VMware KB: ESX error: No free space left on device
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1007638&sliceId=2&docTypeID=DT_KB_1_1&dialogID=595766083&stateId=1%200%20595772201
KNOWN ISSUE!!!
VMware KB: ESXi 5.1 host becomes unresponsive when attempting a vMotion or a configuration change
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2040707
Keywords: vsphere 5.1 update 1 error no space left on device