Forum Discussion

peter_siman's avatar
Icon for Nimbostratus rankNimbostratus
Aug 20, 2020

F5 BIG-IP LTM VE - disk space issue

We do have a cron job running which updates a CRL file on regular basis in order to allow F5 to use up to date CRL file for verification of client certificate during mTLS.


What we have noticed is, that the HDD space is constantly being filled up.

We did some investigation and we found out, that there are always files being created in the ./config/filestore/.trash_bin_d/ folder


Please see below an example


ls -lh ./config/filestore/.trash_bin_d/.backup_1597885592_196_d/Common_d/certificate_revocation_list_d/:Common:trust2408-full_88715_317

ls -lh ./config/filestore/.trash_bin_d/.backup_1597885592_196_d/Common_d/certificate_revocation_list_d/:Common:trust2408-prod_79040_294


trust2408-prod / trust2408-full are the certificate revocation lists created by the script.


This is causing, that the file system below is full and F5 can no longer operate properly


Here is a difference within 24 hours


Status from 19/08/2020

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/vg--db--vda-set.2._config 2.1G 467M 1.5G 24% /config


Status from 20/08/2020

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/vg--db--vda-set.2._config 2.1G 805M 1.2G 41% /config


I see that there are 10 files generate in less than 24 hours, each file has 43M.


At the end of the day it will eat up all free space and cause F5 to not function properly any longer.

I would expect, that these files which are in "./config/filestore/.trash_bin_d/.backup_nnnn " foler are automatically removed by F5 on regular basis. Or am I missing anything here?


We do have 4 F5 load balancers which have this script enabled and only 2 of them have this issue. All the setup is the same.

Has anyone experienced anything similar? Any advice is highly appreciated.

2 Replies

  • Hello Peter.


    Usually, the folder '/config/filestore/.trash_bin_d' is used to store files when the execution of some transaction fails. If you see files there, normally points that the script could be failing in some step. Information in this folder is completely removable, so you could include some sentence like this in your script:

    rm -f /config/filestore/.trash_bin_d/*


    But you can also try with this:


    Debugging your script is also a good point.