Loading...
Loading...
There are hundreds of policy history files for non-existent policies stored under /ts/dms/policy/policy_versions, which might cause /var disk exhaustion.
/var disk usage is high.
There are hundreds of policy history files for non-existent policies stored under /ts/dms/policy/policy_versions. Two possible causes might explain what caused the history files to be copied: -- The device was synchronized from itself. -- There was a UCS loaded on the device.
Use the following one-liner to find unreferenced policy history files that can be deleted: ---------------------------------------------------------------------- perl -MData::Dumper -MF5::DbUtils -MFile::Find -e '$dbh = F5::DbUtils::get_dbh(); $sql = ($dbh->selectrow_array(q{show tables in PLC like ?}, undef, q{PL_POLICY_VERSIONS})) ? q{select policy_version, policy_id from PLC.PL_POLICY_VERSIONS} : q{select revision, policy_id from PLC.PL_POLICY_HISTORY}; %known_history_files = map { (qq{$_->[1]/$_->[0].plc} => 1) } @{$dbh->selectall_arrayref($sql)}; find({ wanted => sub { next unless -f $_; $_ =~ m|/policy_versions/(.*)$|; if (! $known_history_files{$1}) { print qq{$_\n} } }, no_chdir => 1, }, q{/ts/dms/policy/policy_versions});' ---------------------------------------------------------------------- Manually verity the file list output. If it seems correct, you can then delete the files by piping the output into 'xargs rm'. In addition, you can delete the following file: /var/ts/var/install/recovery_db/conf.tar.gz.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.