WARNING: "Cannot extend visorfs file /opt/sut/tmp/libhpsrv.debug_1.log because its ramdisk (sut-tmp) is full."
search cancel

WARNING: "Cannot extend visorfs file /opt/sut/tmp/libhpsrv.debug_1.log because its ramdisk (sut-tmp) is full."

book

Article ID: 407652

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • When this issue occurs, the hostd.log will display the following message:
    The ramdisk 'sut-tmp' is full.
  • As a result, the /opt/sut/tmp/libhpsrv.debug_1.log file cannot be written.
  • Additionally, the vmkernel.log will display the following messages:

    Cannot extend visorfs file /opt/sut/tmp/libhpsrv.debug_1.log because its ramdisk (sut-tmp) is full.
    Admission failure in path: host/system/visorfs/ramdisks/sut-tmp:sut-tmp.

  • Additionally, the vobd.log will display the following message: var/run/log/vobd.log
    vobd [esx.problem.visorfs.ramdisk.full] The ramdisk 'sut-tmp' is full.  As a result, the file /opt/sut/tmp/libhpsrv.debug_1.log could not be written.
  • The host will go in non responding state

Cause

For any HPE platforms running VMware ESXi 8.0 or 9.0, when using Integrated Smart Update Tools (iSUT), any component firmware updates may remain at a pending state in the HPE Integrated Lights-Out (iLO) installation queue. Additionally, iSUT may be unable to reboot the platform after performing the firmware update. As a result, the firmware update will not complete.

When using iSUT 6.1.0 and running in any auto-modes, the ramdisk (sut-tmp) will reach full capacity, even though iSUT is not used in deploying firmware or drivers.

Resolution

Please reach out to the HPE vendor for more information and further assistance. 

Workaround:

Manually remove the libhpsrv.debug_1.log file to clear some space.

rm /opt/sut/tmp/libhpsrv.debug_1.log

Additional Information

As per the HPE advisory , issue is resolved in iSUT 6.2.0 (or later).