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

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.

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:

 

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

Workaround

N/A