Last Modified: Jul 13, 2024
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.2.1, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Mar 19, 2015 Severity: 3-Major
If the BIG-IP system is configured with non-system file objects and those objects are modified, old copies of the object configuration do not always get deleted but instead are saved in the trash bin under /config/filestore/.trash_bin_d.
The stale, backup file object configurations fills up the disk. The trash bin gets cleared only after a successful configuration load.
Non-system file objects are created and configured, and such objects change.
To clear the file objects trash bin in /config/filestore/.trash_bin_d, run the following commands after the file objects are modified or deleted: -- tmsh save /sys config. -- tmsh load /sys config.
Non-system file objects that are deleted or modified still have backup copies saved in the trash bin, but the system now clears the backup copies after successfully saving the configuration. No configuration load is needed.