Bug ID 1045277: The /var partition may become 100% full requiring manual intervention to clear space

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,, 17.0.0,,, 17.1.0,,,, 17.1.1,,,

Opened: Sep 07, 2021

Severity: 3-Major


The /var partition might become completely full on the disk due to files being written to /var/config/rest. This condition may be accompanied by console error messages similar to the following: 011d0004:3: Disk partition /var (slot #) has only 0% free on secondary blade. Additionally, there may be periodic restjavad and bigd daemons restarts related to disk space exhaustion.


The partition housing /var/config/rest may become 100% full, impacting future disk IO to the partition.


Process traffic while DoS Dashboard is open


Important: This workaround is temporary, and may need to be periodically performed either manually or from a script. Impact of Workaround: While these steps are performed, the BIG-IP REST API will be temporarily inaccessible, and higher disk IO may be seen. Run the following commands, in sequence: bigstart stop restjavad rm -rf /var/config/rest/storage*.zip rm -rf /var/config/rest/*.tmp bigstart start restjavad Manual application of these workaround steps clears the 100% utilized space condition and allows the partition to resume normal operation.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips