On Sun, May 20, 2018 at 1:43 AM, Kevin Fenzi kevin@scrye.com wrote:
Greetings.
/mnt/koji is getting low on space, and one thing I noticed is that we still have:
/mnt/koji/mash/
This is the directory we used to use back when we used mash to push updates. It has in it:
221G atomic 59M atomic-updates 160M atomic-updates-logs 1.3T updates
So, nuking this should save us hopefully about 1.5TB.
+1 to this.
Additionally, in /mnt/koji/compose/ we have at least 108 each of:
Fedora-Cloud-26-* Fedora-Docker-26* Fedora-Cloud-27-* Fedora-Docker-27*
These should be moved into a container and cloud sub directory like all the other pungi runs, then the find -mtime +14 can be run on them at the end of each compose like the rest of them. I noticed this some time ago but never got around to filing a ticket/PR to fix it.
How many of those should we keep around?
14 like all the rest of the composes.
Also, we have compose dirs for 26, 27, 28 with all the composes we had for each cycle. Do we want to/need to keep those around any? Should we delete them when a release goes EOL?
I think bodhi uses something around this for builds, as I think does the two week atomic, but someone else that knows both of those better than me can likely confirm.
If anyone sees anything else we are no longer using, please let me know.
Does anyone need/want/see a need for any of the above?
Peter