Blaze4up
Enthusiast
Enthusiast

The ramdisk 'root' is full, and now ?

Jump to solution

Hi guru's,

I'm having  problems with several ESXi 6.5 hosts.

I see in the logs the warning/error that the ramdisk root is full

I can verify that when i  log in to the ESXi host, indeed i see the root ramdisk 100% used.

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M       32M        0B 100% --

etc                        28M      244K       27M   0% --

opt                        32M        0B       32M   0% --

var                        48M      480K       47M   0% --

tmp                       256M        8K      255M   0% --

iofilters                  32M        0B       32M   0% --

hostdstats               1803M       30M     1772M   1% --

But i cannot reveal why..

Is there anyone that can help me ?

Here is some additional information:

The image of the hosts is :DellEMC-ESXi-6.5U1-5969303-A00,  updated to build 7388607

df -h

Filesystem   Size   Used Available Use% Mounted on

NFS          2.0T   2.0G      2.0T   0% /vmfs/volumes/datastore5

NFS          4.0T   2.6T      1.4T  65% /vmfs/volumes/datastore4

VMFS-6     103.5G   7.7G     95.8G   7% /vmfs/volumes/datastore1

VMFS-6       1.7T   1.3T    464.5G  74% /vmfs/volumes/datastore2

VMFS-5       9.9T   7.3T      2.6T  74% /vmfs/volumes/datastore3

vfat         4.0G   6.3M      4.0G   0% /vmfs/volumes/59c8f1c8-a26e78a7-99b0-a0369fc27e68

vfat       249.7M 153.1M     96.6M  61% /vmfs/volumes/54365377-c3c5b89a-5c86-13bc99ec6faf

vfat       285.8M 206.7M     79.1M  72% /vmfs/volumes/59c8f1c2-d888df26-d390-a0369fc27e68

vfat       249.7M 153.0M     96.7M  61% /vmfs/volumes/3e21e27e-026410fb-1b44-492d456aa0b4

/var/log/vmkernel.log

2018-02-21T01:13:35.558Z cpu45:66064)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/vpxa.0.gz because its ramdisk (root) is full.

2018-02-21T01:20:48.363Z cpu34:65864)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/iofiltervpd.log because its ramdisk (root) is full.

2018-02-21T01:21:00.016Z cpu55:65866)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/hostd.log because its ramdisk (root) is full.

2018-02-21T01:21:18.363Z cpu6:65865)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/storagerm.log because its ramdisk (root) is full.

2018-02-21T01:21:18.363Z cpu33:65863)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/rhttpproxy.log because its ramdisk (root) is full.

2018-02-21T01:30:18.367Z cpu28:65863)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/hostd-probe.log because its ramdisk (root) is full.

2018-02-21T01:32:18.368Z cpu28:65863)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/sdrsinjector.log because its ramdisk (root) is full.

2018-02-21T01:43:36.080Z cpu49:66064)WARNING: VisorFSRam: 353: Cannot extend visorfs file /scratch/log/vpxa.0.gz because its ramdisk (root) is full.

0 Kudos
1 Solution

Accepted Solutions
Blaze4up
Enthusiast
Enthusiast

After a long search it turned out to be a bug in the base image.

After an installation of the new base image, the problem was solved.

View solution in original post

0 Kudos
2 Replies
SureshKumarMuth
Commander
Commander

Did you check what is there inside root partition and causing the issue ?

Check if this helps you if you have not tried before

Solved: Root partition full after ESXi 6.5 upgrade and MEM... - Dell Community

Also check how is your scratch partition is configured.

Regards, Suresh https://vconnectit.wordpress.com/
0 Kudos
Blaze4up
Enthusiast
Enthusiast

After a long search it turned out to be a bug in the base image.

After an installation of the new base image, the problem was solved.

View solution in original post

0 Kudos