mw-log is really activity log, for all activities in my php bot, which is actually $wgDebugLogFile. There was a time people asked me "why my bot is doing (something) in (some way)" and the situation was difficult to reproduce. The only use of those files (until now) is to answer those questions for people (and sometimes for myself).

sql/dumps contains database dumps of my user databases on replica servers. Since that service is declared as "unreliable" I have to make my own backups. Previous uses were like T126946.

I‘m running these currently

tools.liangent-php@tools-bastion-03:~/mw-log$ find . -mtime +90 -delete
tools.liangent-php@tools-bastion-03:~/sql/dumps$ rm -rf 2013* & rm -rf 2014* & rm -rf 2015*

but some long-term solution is needed.

thank you @liangent for responding.

@liangent I was looking at old bugs today and ran across this one. Your tool's total disk usage is smaller than before (61G total), but still quite large. 56G of the files are in your $HOME/sql/dumps directory. These files are sql dumps of various projects timestamped from 2016-01-01 to 2017-12-13.

Would you be willing to clean up those files now too?

@liangent Looking closer at your liangent-php tool, I do not see strong signs that it has been in use since 2019-03-25. I have added T253818: Clean up NFS disk hogs that are abandoned as a parent task here to track this apparent abandonment.

Can you please respond as to whether you are still using this tool or not?

Based on the info from T136208#2327065 I have cleaned up old backups in the $HOME/sql/dumps directory. I deleted all of them from prior to 2017-12-01 and compressed the remaining files. This had reduced the total disk usage for your tool from the 61G value mentioned in T136208#6149197 to 5.3G.

If you start using the tool again, I would strongly suggest that you compress your database dumps at the time they are created and also add a pruning job that limits your total backup count to some reasonable number like 7 or 14 total backups at any given time.