PA-220 disk utilization in / and /opt/pancfg partitions

PA-220 disk utilization in / and /opt/pancfg partitions

2652
Created On 08/07/25 16:10 PM - Last Modified 08/11/25 14:11 PM


Symptom


  • Critical System Log message "Disk usage for / exceeds limit, 9x percent in use, cleaning filesystem".
  • Critical System Log message "Disk usage for /opt/pancfg exceeds limit, 80 percent in use"


Environment


**Product_versions**
• PAN-OS 10.2.x
**Hardware Details**
• PA-220



Cause


PA-220 platform has a relatively small system disk and has been susceptible to experiencing alerts related to high disk space utilization system log messages even under normal operating conditions. 



Resolution


**REMEDIATION_PLAN**
For /opt/pancfg utilization

  1. Limit the number of dynamic update images to retain on the firewall to 2 with the following command
    1.  > set max-num-images count 2

                  ****NOTE: Even with this setting during the download and installation process of a new dynamic update the /opt/pancfg utilization may exceed 80%, thereby triggering the /opt/pancfg system log.  When the download and installation process completes the oldest version is removed and the disk utilization should return to under the 80% threshold.  

 

For root partition utilization

  1. Enable aggressive cleaning option
    1.  > debug software disk-usage aggressive-cleaning enable

    2. For the PA-220 platform that will start the cleanup when root partition utilization reaches 90%.  The PA-220 platform will run in high 80s/low 90s utilization.  If utilization is stuck above 94% please open a TAC case so more detailed analysis of partition use can be done. 

  2. Can periodically run deep cleaning command 
    1. > debug software disk-usage cleanup deep threshold [90-100]
    2. which will delete backup log files and other temporary data until the disk usage is reduced to the specified threshold

       If the following error message shows up after the disk-usage cleanup deep threshold 90 command:
            Server error : op command for client dagger timed out as client is not available
      Then start with a higher threshold example 94 instead of 90 so the cleaning time will be less which will prevent the server timeout error.
      > debug software disk-usage cleanup deep threshold 94
      You can afterwards keep lowering the threshold value to reach 90.



Additional Information


Other articles that are relevant 
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000g1EMCAY
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClaJCAS



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA1Ki000000TNjlKAG&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail