Summary

Example

When an administrator manually copies files to the host and accidentally uses an incorrect path (that is, one outside /vmfs/volumes), this error message appears:

The ramdisk 'root' is full. As a result, the file /testfile could not be written.

Also, in the /var/log/vmkernel.log file, you may see the error:

VisorFSRam: 233: Cannot extend visorfs file /var/lib/vmware/hostd/journal/ because its ramdisk (root) is full.
 

Impact

Files on the affected RAM disk can no longer be extended.

Various administrative actions depend on the ability to write files to various parts of the root file system and may fail if a RAM disk is full.

VMware vSphere ESXi 6.0
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vSphere ESXi 7.0.0

1. SSH to the affected ESXi host
2. To view the ramdisk, run: $ vdf -h
3. Identify files in the root directory larger than 1 MB: $ find / -size +1024k -exec du -h {} \; | less
4. Old/stale left over ESXi host log bundles should be copied/moved off and removed to provide space back to the ESXi host 

• Investigating disk space on an ESX or ESXi host (1003564)
• Creating a persistent scratch location for ESXi 4.x and 5.x (1033696)
• ESXi 5.1 host becomes unresponsive when attempting a vMotion migration or a configuration change (2040707)
• /var/log/wtmp grows rapidly and fills the ramdisk of the ESXi host (2019021)
• ESXi RAM disk full due to a locked virtual machine log file (2057975)

Additional Information

For translated versions of this article, see:

• 日本語: RAM ディスクの空き領域がない (2093496)
• 简体中文: 内存磁盘已满 (2095104)