This article indicates that one of the possible reasons for the /var partition usage is high alarm to be seen on QFX devices is the presence of "tm" files in the device storage, which are taking up a lot of the space in the device partition.
/var partition usage is high
The following alarm is seen on the QFX device:
user@sw1> show chassis alarms Dec 11 00:23:15 1 alarm currently active Alarm time Class Description 2020-12-10 20:51:14 UTC Minor RE 0 /var partition usage is high
% du -cks * | sort -rn du: cron/tabs: Permission denied du: db/certs/common: Permission denied du: db/certs/system-key-pair: Permission denied du: db/certs/system-cert: Permission denied du: db/entropy: Permission denied du: db/jdhcp_snoop: Permission denied du: heimdal: Permission denied du: mfs/var/cron/tabs: Permission denied du: mfs/var/db/entropy: Permission denied du: mfs/var/heimdal: Permission denied du: mfs/var/spool/opielocks: Permission denied du: spool/opielocks: Permission denied 440780 total 348080 tm <<<< This file in /var 40714 rundb 38254 packages 11782 log 892 mfs 804 db 98 etcroot
In some scenarios, a file named " tm " gets created in /var on the device. This file being large in size triggers a minor alarm for storage on the device as shown above.
tm
/var
This file is not detected during storage cleanup/troubleshooting.
user@sw1> request system storage cleanup dry-run fpc0: -------------------------------------------------------------------------- List of files to delete: Size Date Name 9785B Dec 11 16:58 /var/log/bgp.log.0.gz 9855B Dec 11 14:28 /var/log/bgp.log.1.gz 9839B Dec 11 11:58 /var/log/bgp.log.2.gz 9894B Dec 11 09:28 /var/log/bgp.log.3.gz 9840B Dec 11 06:58 /var/log/bgp.log.4.gz 9821B Dec 11 04:28 /var/log/bgp.log.5.gz 9791B Dec 11 01:58 /var/log/bgp.log.6.gz 151B Dec 11 19:23 /var/log/default-log-messages.0.gz 139B Dec 11 19:23 /var/log/firewall.0.gz 13.9K Dec 11 19:23 /var/log/interactive-commands.0.gz 199B Dec 11 19:23 /var/log/messages.0.gz 135B Dec 11 19:23 /var/log/mpls.0.gz 4080B Dec 11 19:23 /var/log/syslog.0.gz 9915B Dec 11 18:15 /var/log/syslog.1.gz 8993B Dec 11 15:00 /var/log/syslog.2.gz 9473B Dec 11 11:45 /var/log/syslog.3.gz 9939B Dec 11 08:45 /var/log/syslog.4.gz 9182B Dec 11 05:45 /var/log/syslog.5.gz 10.3K Dec 11 02:30 /var/log/syslog.6.gz 3184B Dec 11 19:23 /var/log/wtmp.0.gz 27B Dec 10 23:41 /var/log/wtmp.1.gz
As can be seen above, the file is not recognized in the storage cleanup output.
storage cleanup
This file is not part of any default process/daemon but gets created when a customized/guest VM is spun on QFX5100. See Launching a Guest Virtual Machine (VM) to Run a Third Party Application on Junos OS Release 13.2X51-D20 and Later .
This file is not part of any process/daemon running on the device. Therefore, deleting the file will not have any impact on the basic functionality of the device. However, ensure that you delete this file during a Maintenance Window. If the file appears again or any other issue is encountered due to the file, contact Support to investigate the problem further.
To delete the file, you need to have root access:
root@sw1>file delete /var/tm root@sw1>file list /var details >>> Validate if file is deleted. root@sw1> show chassis alarms >>> Confirm whether the alarm is cleared.