VMware Cloud Community
rschmid
Enthusiast
Enthusiast
Jump to solution

Error "The ramdisk 'tmp' is full"

Hello,

I need help with an error message of one of our vpshere host.

These are is the error messages:

The ramdisk 'tmp' is full.  As a result, the file

/tmp/.SwapInfoSysSwap.lock.LOCK.33980 could

not be written.

error

05.03.2014 11:06:10

The ramdisk 'tmp' is full.  As a result, the file

/tmp/auto-backup.3430163/local.tgz could not be

written.

error

05.03.2014 11:58:40


The ramdisk 'tmp' is full.  As a result, the file

/tmp/auto-backup.3439408/local.tgz could not be

written.

error

05.03.2014 12:58:40

The ramdisk 'tmp' is full.  As a result, the file

/tmp/auto-backup.3458439/local.tgz could not be

written.

error

05.03.2014 14:58:39

The ramdisk 'tmp' is full.  As a result, the file

/tmp/auto-backup.3467650/local.tgz could not be

written.

error

05.03.2014 15:58:39

Why is the ramdisk full or why cannot be written to it ?


Kind regards,

Roland

1 Solution

Accepted Solutions
jrmunday
Commander
Commander
Jump to solution

It looks like this is a known bug, and the workaround is to clear the log down;

http://wp.alphaparallel.com/2013/10/vmware-esxi-ram-disk-full-due-to-adaptecs-arcconf-bug/

This article is a few months old, so perhaps there is a fix already.

My assumption on the basis that it is logging to tmp is that the log contents are not critical to any operation and would clear them down until a fix is available.

Cheers,

Jon

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77

View solution in original post

Reply
0 Kudos
8 Replies
vJJSosa
Enthusiast
Enthusiast
Jump to solution

Hi, that's sound as /tmp full, please check if you copy some files accidentally

Regards

[VCAP5-DCA, VCP3/4/5, VCP-DT4, MCITP Network Infrastructure, HP ASE Bladesystem]
Reply
0 Kudos
rschmid
Enthusiast
Enthusiast
Jump to solution

vJJSosa schrieb:

Hi, that's sound as /tmp full, please check if you copy some files accidentally

Regards

Hi,

no, not really.

/tmp # ls -al

total 196616

drwxrwxrwt    1 root     root           512 Mar  5 16:01 .

drwxr-xr-x    1 root     root           512 Mar  5 16:17 ..

-rw-r--r--    1 root     root     201322489 Mar  5 16:20 arcconf.log

-rw-r--r--    1 root     root             0 Mar  5 16:01 bootbank.lck

-rw-------    1 root     root            36 Mar  5 16:20 probe.session

Kind regards,

Roland

Reply
0 Kudos
jrmunday
Commander
Commander
Jump to solution

Hi Roland,

How much free "tmp" space do you see when running the below command;

~ # esxcli system visorfs ramdisk list

Ramdisk Name  System   Reserved     Maximum      Used  Peak Used  Free  Reserved Free  Maximum Inodes  Allocated Inodes  Used Inodes  Mount Point

------------  ------  ---------  ----------  --------  ---------  ----  -------------  --------------  ----------------  -----------  ---------------------------

root            true  32768 KiB   32768 KiB   468 KiB    472 KiB  98 %           98 %            8192              4096         3525  /

etc             true  28672 KiB   28672 KiB   148 KiB    176 KiB  99 %           99 %            4096              1024          459  /etc

tmp            false   2048 KiB  196608 KiB     8 KiB    188 KiB  99 %           99 %            8192               256            4  /tmp

hostdstats     false      0 KiB   84992 KiB  1240 KiB   1240 KiB  98 %            0 %            8192                32            4  /var/lib/vmware/hostd/stats

Cheers,

Jon

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77
Reply
0 Kudos
Shrikant_Gavhan
Enthusiast
Enthusiast
Jump to solution

I had the same issue, When I called vmware support they suggested me to move some of these files to other location. When asked about the files, that engineer could not answer me. He just said that these files are created by esxi .

If you know the reason, please share.

VMware KB: RAM disk is full

Thanks and Regards, Shrikant Gavhane
Reply
0 Kudos
rschmid
Enthusiast
Enthusiast
Jump to solution

jrmunday schrieb:

Hi Roland,

How much free "tmp" space do you see when running the below command;

~ # esxcli system visorfs ramdisk list

Ramdisk Name  System   Reserved     Maximum      Used  Peak Used  Free  Reserved Free  Maximum Inodes  Allocated Inodes  Used Inodes  Mount Point

------------  ------  ---------  ----------  --------  ---------  ----  -------------  --------------  ----------------  -----------  ---------------------------

root            true  32768 KiB   32768 KiB   468 KiB    472 KiB  98 %           98 %            8192              4096         3525  /

etc             true  28672 KiB   28672 KiB   148 KiB    176 KiB  99 %           99 %            4096              1024          459  /etc

tmp            false   2048 KiB  196608 KiB     8 KiB    188 KiB  99 %           99 %            8192               256            4  /tmp

hostdstats     false      0 KiB   84992 KiB  1240 KiB   1240 KiB  98 %            0 %            8192                32            4  /var/lib/vmware/hostd/stats

Cheers,

Jon

Hi Jon,

our "tmp" has no space left, 196608 KiB used of 196608 KiB Maximum space available.

~ # esxcli system visorfs ramdisk list

Ramdisk Name  System   Reserved     Maximum        Used   Peak Used  Free  Reserved Free  Maximum Inodes  Allocated Inodes  Used Inodes  Mount Point        

------------  ------  ---------  ----------  ----------  ----------  ----  -------------  --------------  ----------------  -----------  ---------------------------

root            true  32768 KiB   32768 KiB    1792 KiB    1800 KiB  94 %           94 %            8192              4096         3669  /                  

etc             true  28672 KiB   28672 KiB     204 KiB     232 KiB  99 %           99 %            4096              1024          486  /etc               

tmp            false   2048 KiB  196608 KiB  196608 KiB  196608 KiB   0 %            0 %            8192               256            4  /tmp               

hostdstats     false      0 KiB  808960 KiB    3168 KiB    3168 KiB  99 %            0 %            8192                32            5  /var/lib/vmware/hostd/stats

the file arcconf.log is very large.

/tmp # ls -l

total 196608

-rw-r--r--    1 root     root     201322489 Mar  6 07:53 arcconf.log

-rw-r--r--    1 root     root             0 Mar  6 07:01 bootbank.lck

-rw-------    1 root     root            36 Mar  6 07:50 probe.session

Do I need all the log entries of arcconf.log ? Need more space.

Kind regards,

Roland

Reply
0 Kudos
jrmunday
Commander
Commander
Jump to solution

It looks like this is a known bug, and the workaround is to clear the log down;

http://wp.alphaparallel.com/2013/10/vmware-esxi-ram-disk-full-due-to-adaptecs-arcconf-bug/

This article is a few months old, so perhaps there is a fix already.

My assumption on the basis that it is logging to tmp is that the log contents are not critical to any operation and would clear them down until a fix is available.

Cheers,

Jon

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77
Reply
0 Kudos
rschmid
Enthusiast
Enthusiast
Jump to solution

jrmunday schrieb:

It looks like this is a known bug, and the workaround is to clear the log down;

http://wp.alphaparallel.com/2013/10/vmware-esxi-ram-disk-full-due-to-adaptecs-arcconf-bug/

This article is a few months old, so perhaps there is a fix already.

My assumption on the basis that it is logging to tmp is that the log contents are not critical to any operation and would clear them down until a fix is available.

Cheers,

Jon

Hi Jon,

thanks for the link, arcconf.log is growing very fast.

Want to add a cron job, but cannot edit /var/spool/cron/crontabs/root on my host (file is readonly).

I wasn't in touch with linux OS for many years, how do I edit the file root to add my cron job ?

Kind regards,

Roland

Reply
0 Kudos
rschmid
Enthusiast
Enthusiast
Jump to solution

perfect now it works fine Smiley Happy