Disk usage for / exceeds limit, 95 percent in use.

Announcements

ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

Reply
Highlighted
L1 Bithead

Disk usage for / exceeds limit, 95 percent in use.

I know there have been several messages about this issue, but so far, the only solution Palo Alto has given, is to update to a new version. We have followed PA suggestions and months after the update, the issue starts again and their solution will be to update to a new version.

 

Firewall model: PA-5060

Software version: 8.1.10

 

fw1(active)> show system files

/var/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/var/cores/crashinfo:
total 0

/opt/var.dp2/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/opt/var.dp2/cores/crashinfo:
total 0

/opt/var.dp1/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/opt/var.dp1/cores/crashinfo:
total 0

/opt/var.dp0/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/opt/var.dp0/cores/crashinfo:
total 0

/opt/panlogs/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/opt/panlogs/cores/crashinfo:
total 0

/opt/var.cp/cores/:
total 4.0K
drwxr-xr-x 2 root root 4.0K Aug 2 2018 crashinfo

/opt/var.cp/cores/crashinfo:
total 0

 

Is there any other solution that is not updating to a new OS version?

 

Thanks.

Tags (2)
Highlighted
Cyber Elite

@KatiaNunez,

What's your actual version number, because it's not 8.1.10. Assuming that you meant 8.0.10 then you could still be running into the following:

 

PAN-96522: Fixed an intermittent issue where the firewall did not rotate error logs correctly, which caused disk space issues.

Addressed in 8.0.14

 

PAN-92958: Fixed an issue where disk utilization increased unnecessarily because the firewall did not archive and rotate the /var/on file, which therefore grew to over 40MB.

Addressed in 8.0.11

 

You could simple remove the extra logs by reviewing the mp-log and dp-log and cp-log entries and making sure that you don't have anything keeping an odd number of old logs. You can remove anything with a .old.* and .old entries to clear system space. 

Unfortunately bugs like this don't get found under normal testing due to how long it takes to generate most of these logs.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!