Disk space & OS upgrades

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Disk space & OS upgrades

L4 Transporter

I regularly update the OS to the next recommended version every other month, and I was wondering if there was anything that has to be done  to clean up the hard drive so as not to run out of space?

31 REPLIES 31

L4 Transporter

This is what the disk space shows today

 

Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 2.6G 1018M 73% /
/dev/md5 7.6G 3.1G 4.1G 44% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 52% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 117G 71G 63% /opt/panlogs

 

Hi,

 

Your disk usage looks ok to me. What model of the hardware do you have? Is it increasing constantly or going up and down?

 

Thx,

Myky

To add onto this; you can delete the old images off of the device that you are no longer using. That being said your storage numbers look fine and I wouldn't really worry about deleting off old images unless you need the space back. 

What do you mean by old images? 

It is a PA 5050 and I have tracked it over the past 2 years - so does it maintain a certain amount without manually interactions?

 

6/8/2015

Filesystem Size Used Avail Use% Mounted on
/dev/md2 3.8G 2.3G 1.4G 63% /
/dev/md5 7.6G 2.9G 4.3G 40% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 52% /opt/panrepo
tmpfs 2.0G 69M 1.9G 4% /dev/shm
/dev/md8 198G 94G 94G 51% /opt/panlogs

jprovine@sis-pamgt(active)>

8/29/2016
Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 3.1G 566M 85% /
/dev/md5 7.6G 3.1G 4.2G 43% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 53% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 114G 75G 61% /opt/panlogs


1/17/2017
jprovine@sis-pamgt(active)>show system disk-space

Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 2.6G 1018M 73% /
/dev/md5 7.6G 3.1G 4.1G 44% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 52% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 117G 71G 63% /opt/panlogs

Once the image is no longer needed you can delete it from hard disk:

 

image.PNG

Okay good to know! So I have never done that before and my numbers seem to never go over 85% at this point, do these images drop off on their own, or when you upgrade to another version,  Is any manual intervention needed?

All the time you have to do that manually. Image will stay unless you delete

so any idea how these number changed ?

 

6/8/2015

Filesystem Size Used Avail Use% Mounted on
/dev/md2 3.8G 2.3G 1.4G 63% /
/dev/md5 7.6G 2.9G 4.3G 40% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 52% /opt/panrepo
tmpfs 2.0G 69M 1.9G 4% /dev/shm
/dev/md8 198G 94G 94G 51% /opt/panlogs

jprovine@sis-pamgt(active)>

8/29/2016
Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 3.1G 566M 85% /
/dev/md5 7.6G 3.1G 4.2G 43% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 53% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 114G 75G 61% /opt/panlogs


1/17/2017
jprovine@sis-pamgt(active)>show system disk-space

Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 2.6G 1018M 73% /
/dev/md5 7.6G 3.1G 4.1G 44% /opt/pancfg
/dev/md6 3.8G 1.9G 1.8G 52% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 117G 71G 63% /opt/panlogs

1) /dev/md2 3.8G 2.3G 1.4G 63% / - root partition. Not much you can do with it but some technics below

 

https://live.paloaltonetworks.com/t5/Featured-Articles/DotW-Disk-space-issue-on-root/ta-p/71914

 

2) /dev/md8 198G 114G 75G 61% /opt/panlogs - partition wrehe your logs are retains (depents on the configuration will be purged)

 

check config:

 

> show system logdb-quota

 

https://live.paloaltonetworks.com/t5/Management-Articles/When-are-Logs-Purged-on-the-Palo-Alto-Netwo...

 

not sure about other partitions. Maybe other members can add/correct 

I ran the show system files and this is what I got, there doesn't appear to be much there

 

/var/cores/:
total 4.0K
drwxrwxrwx 2 root root 4.0K Nov 29 07:20 crashinfo

/var/cores/crashinfo:
total 0

/opt/var.cp/cores/:
total 4.0K
drwxrwxrwx 2 root root 4.0K Nov 29 07:23 crashinfo

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

/opt/var.dp1/cores/:
total 4.0K
drwxrwxrwx 2 root root 4.0K Nov 29 07:23 crashinfo

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

/opt/var.dp0/cores/:
total 4.0K
drwxrwxrwx 2 root root 4.0K Nov 29 07:23 crashinfo

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

 

 

jprovine@sis-pamgt(active)> show system logdb-quota

Quotas:
              system: 4.00%, 7.620 GB Expiration-period: 0 days
              config: 4.00%, 7.620 GB Expiration-period: 0 days
               alarm: 3.00%, 5.715 GB Expiration-period: 0 days
             appstat: 4.00%, 7.620 GB Expiration-period: 0 days
         hip-reports: 1.00%, 1.905 GB Expiration-period: 0 days
             traffic: 32.00%, 60.958 GB Expiration-period: 0 days
              threat: 16.00%, 30.479 GB Expiration-period: 0 days
               trsum: 7.00%, 13.335 GB Expiration-period: 0 days
         hourlytrsum: 3.00%, 5.715 GB Expiration-period: 0 days
          dailytrsum: 1.00%, 1.905 GB Expiration-period: 0 days
         weeklytrsum: 1.00%, 1.905 GB Expiration-period: 0 days
              urlsum: 2.00%, 3.810 GB Expiration-period: 0 days
        hourlyurlsum: 1.00%, 1.905 GB Expiration-period: 0 days
         dailyurlsum: 1.00%, 1.905 GB Expiration-period: 0 days
        weeklyurlsum: 1.00%, 1.905 GB Expiration-period: 0 days
               thsum: 2.00%, 3.810 GB Expiration-period: 0 days
         hourlythsum: 1.00%, 1.905 GB Expiration-period: 0 days
          dailythsum: 1.00%, 1.905 GB Expiration-period: 0 days
         weeklythsum: 1.00%, 1.905 GB Expiration-period: 0 days
              userid: 1.00%, 1.905 GB Expiration-period: 0 days
   application-pcaps: 1.00%, 1.905 GB Expiration-period: 0 days
             extpcap: 1.00%, 1.905 GB Expiration-period: 0 days
  debug-filter-pcaps: 1.00%, 1.905 GB Expiration-period: 0 days
            dlp-logs: 1.00%, 1.905 GB Expiration-period: 0 days
            hipmatch: 3.00%, 5.715 GB Expiration-period: 0 days

Disk usage:
traffic: Logs and Indexes: 61G Current Retention: 2 days
threat: Logs and Indexes: 11G Current Retention: 842 days
system: Logs and Indexes: 5.1G Current Retention: 1030 days
config: Logs and Indexes: 1.9G Current Retention: 1009 days
trsum: Logs and Indexes: 14G Current Retention: 38 days
hourlytrsum: Logs and Indexes: 5.6G Current Retention: 6 days
dailytrsum: Logs and Indexes: 1.9G Current Retention: 27 days
weeklytrsum: Logs and Indexes: 2.0G Current Retention: 199 days
thsum: Logs and Indexes: 3.8G Current Retention: 842 days
hourlythsum: Logs and Indexes: 2.0G Current Retention: 471 days
dailythsum: Logs and Indexes: 1.2G Current Retention: 841 days
weeklythsum: Logs and Indexes: 429M Current Retention: 836 days
appstatdb: Logs and Indexes: 3.8G Current Retention: 1006 days
userid: Logs and Indexes: 11M Current Retention: 1006 days
hipmatch: Logs and Indexes: 28K Current Retention: 0 days
extpcap: Logs and Indexes: 2.0G Current Retention: 656 days
urlsum: Logs and Indexes: 1.5M Current Retention: 0 days
hourlyurlsum: Logs and Indexes: 1.5M Current Retention: 0 days
dailyurlsum: Logs and Indexes: 1.5M Current Retention: 0 days
weeklyurlsum: Logs and Indexes: 216K Current Retention: 0 days
application: Logs and Indexes: 1.7G Current Retention: 59 days
filters: Logs and Indexes: 15M Current Retention: 299 days
dlp: Logs and Indexes: 4.0K Current Retention: 0 days
hip_report_base: Logs and Indexes: 1.1M Current Retention: N/A
wildfire: Logs and Indexes: 47M Current Retention: N/A

old software versionold software versionI looked and it does not seem as though there is a way to delete these really old os versions

 

 

 

Hi,

 

They are not even downloaded as you still have an option to download each, so no worries

  • 6193 Views
  • 31 replies
  • 0 Likes
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 LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!