Disk Usage alarm on /tftpboot

book

Article ID: 167766

calendar_today

Updated On:

Products

XOS

Issue/Introduction

This article shows how to find out the reasons for a disk usage alarmThe type of alarm reported similar to following means that /tftpboot space is highly utilized:

CBS# show alarms active major
Active Alarms Summary:

Source Critical Major Minor
------ -------- ----- -----
cp2    0        1     1
Total  0        1     1


* indicates an alarm that can be cleared with the 'clear alarms' CLI command

Major:

ID   Date            Source  Description
--                   ----    ------ -----------
1008 Feb 12 04:28:17 cp2     Disk utilization (81%) /tftpboot

Cause

Some reasons why data written by one or more VAP groups might grow to alarm levels are:
  • application is logging to local filesystem
  • application was left with debug log level enabled
  • old VAP group backups might be present in /tftpboot/archives directory
The goal is to find out which files are the top consumers and identify if they can be safely deleted or moved to a remote machine.

Resolution

There are multiple ways to find out top disk space consumers, for example the Unix level command du:

# du -hs /tftpboot/* | sort -nr | head

This command shows space occupied by each directory under /tftpboot folder. This directory contains images for VAPs and therefore typically counted in GBs.

If any directory takes significantly more space, you can drill down and see which sub-directories take most of the space, for example:

# du -hs /tfptboot/<subdirectory>/*

To display the largest files in /tftpboot with size over 10MB, you can use this command:

# find /tftpboot -type f -size +10M -exec ls -lh {} \; | awk '{ print $5 ": " $9 }' | sort -rn

Another option is to use the XOS CLI command  show disk-usage history to see how disk space utilization changes over time:


CBS# show disk-usage history
======================================================================
Top Disk Users Report for Mon Dec 30 04:02:03 CET 2013
======================================================================
 
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md7              11811952   2762840   8449092  25% /
/dev/md1                102672      7984     89472   9% /boot
/dev/mapper/d1vg0-lv0
                       1971472    137488   1733840   8% /cbconfig
/dev/mapper/d1vg1-lv0
                      37353008   6694388  28761148  19% /tftpboot
/dev/mapper/d1vg1-lv1
                       2011792    111844   1797756   6% /mgmt
 
 
======================================================================
Top Disk Users Report for Tue Dec 31 04:02:03 CET 2013
======================================================================
 
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md7              11811952   2758672   8453260  25% /
/dev/md1                102672      7984     89472   9% /boot
/dev/mapper/d1vg0-lv0
                       1971472    137560   1733768   8% /cbconfig
/dev/mapper/d1vg1-lv0
                      37353008   6696712  28758824  19% /tftpboot
/dev/mapper/d1vg1-lv1
                       2011792    111868   1797732   6% /mgmt
 
...etc
 

The Unix level command /usr/os/bin/cbs_disk_usage can be used to find the largest files on each VAP (some output omitted):


# /usr/os/bin/cbs_disk_usage
======================================================================
Top Disk Users Report for Fri Jan 10 18:33:44 CET 2014
======================================================================
 
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/md7              11811952   2785724   8426208  25% /
/dev/md1                102672      7984     89472   9% /boot
/dev/mapper/d1vg0-lv0
                       1971472    139388   1731940   8% /cbconfig
/dev/mapper/d1vg1-lv0
                      37353008   6732600  28722936  19% /tftpboot
/dev/mapper/d1vg1-lv1
                       2011792    112024   1797576   6% /mgmt
 
apm_shared
  16777336 apm_shared/Firmware/AP/apm50_fpga_0207_diag_0504.dat
  16777336 apm_shared/Firmware/AP/ap9600_fpga_0207_diag_0504.dat
   3276920 apm_shared/Firmware/AP/apcp6_fpga_a1.dat
   3276920 apm_shared/Firmware/AP/apcp65_fpga_0600.dat
   3276896 apm_shared/Firmware/AP/apm2030_fpga_R0001.dat
 
...
 
fw_1
 135416832 fw_1/var/opt/CPsuite-R75.40VS/fw1/conf/appfw/appfw_tables.sqlite
  53087885 fw_1/var/opt/CPsuite-R75.40VS/fw1/av/kav/setup/kav8.tar.gz
  50460672 fw_1/opt/CPsuite-R75.40VS/fw1/oracle_oi/oracle_sdk.tar
  28932444 fw_1/var/opt/CPsuite-R75.40VS/fw1/tmp/Check_Point_Arkanoid_Agent_pkg.tgz
  16777336 fw_1/crossbeam/etc/Firmware/AP/apm50_fpga_0207_diag_0504.dat

Presence of VAP group backups created in the past might be verified by running CLI command:

# archive-vap-group show

To remove these old backups, run:

# archive-vap-group delete vap-group <name> archive <number>

 

Workaround

N/A