Virtual machine becomes unresponsive with the log error: Couldn't allocate journal. Garbage collect on volume

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Virtual machine becomes unresponsive
• ESX/ESXi host may become disconnected from vCenter Server or vSphere Client
• The vmkernel or messages log show messages similar to:

Jan 29 05:00:28 vm1 vmkernel: 167:16:14:25.896 cpu1:4106)J3: 1275: Couldn't allocate journal. Garbage collect on volume 492d6928-eb8248a8-f591-0015c5f063c8

Jan 29 05:00:44 vm1 vmkernel: 167:16:14:41.994 cpu2:4106)FS3: 4330: 0 HB slot(s) have been garbage collected

Jan 29 05:16:47 vm1 vmkernel: 167:16:30:45.283 cpu0:4106)J3: 1275: Couldn't allocate journal. Garbage collect on volume 492d6928-eb8248a8-f591-0015c5f063c8

Jan 29 05:17:03 vm1 vmkernel: 167:16:31:01.401 cpu0:4106)FS3: 4330: 0 HB slot(s) have been garbage collected

Jan 29 05:27:36 vm1 vmkernel: 167:16:41:33.759 cpu2:4105)J3: 1275: Couldn't allocate journal. Garbage collect on volume 492d6928-eb8248a8-f591-0015c5f063c8

Jan 29 05:27:52 vm1 vmkernel: 167:16:41:49.848 cpu2:4105)FS3: 4330: 0 HB slot(s) have been garbage collected

Environment

VMware ESXi 3.5.x Installable
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.0
VMware ESX Server 3.5.x
VMware ESXi 4.1.x Embedded
VMware ESXi 4.0.x Embedded
VMware ESXi 4.1.x Installable
VMware ESX 4.0.x
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 5.5

Cause

This issue occurs when the volume is nearing 100% of the used capacity.

Resolution

To resolve this issue, free up space on the volume. For more information, see Troubleshooting a datastore or VMFS volume that is full or near capacity (1003412)

Additional Information

Troubleshooting a datastore or VMFS volume that is full or near capacity