Page MenuHomePhabricator

wdumps custom generated dumps storage space
Closed, ResolvedPublic

Description

@bennofs The wdumps tool is currently the largest consumer of NFS storage in the tools project space. We're running short on available storage and wondering if it's possible to remove some of the recently created dumps.

In total the generated dumps are using 773 gigabytes of storage, any space you can help reclaim would be greatly appreciated.

Event Timeline

Toolforge has 8TB of storage for everyone including both users and tools. @bennofs's tool is currently using ~9% of all storage to host 123 data files. It is also not obvious if the tool has any cleanup mechanism at all for older files.

Sorry for that, I'll look into automating the cleanup.

Sorry for that, I'll look into automating the cleanup.

Thank you @bennofs. In the mean time can you please manually delete some of the custom dumps? We're at 90% storage utilization and fighting off our monitoring alarms.

JHedden moved this task from Inbox to Watching on the cloud-services-team (Kanban) board.

@bennofs, this tool is currently consuming about 225Gb of disk space. Can you please update us about your plan for automating cleanup? And, a quick by-hand cleanup would help keep things moving in the meantime.

Thanks!

@bennofs @mkroetzsch This needs to be cleaned up. You are now at 310.95 GB and tools NFS is filling up.

Please take manual action and do something to automate this as well. I can definitely go start deleting things, but I expect that will break the tool since I don't know what I'm doing.

@bennofs @mkroetzsch This needs to be cleaned up. You are now at 310.95 GB and tools NFS is filling up.

Please take manual action and do something to automate this as well. I can definitely go start deleting things, but I expect that will break the tool since I don't know what I'm doing.

Responses here seem to have been non-existent, so I reported in their github project as well: https://github.com/bennofs/wdumper/issues/31

I've moved the dump files to scratch for now, hope this helps. I also manually cleaned up some big dumps.

There is already a cron task that deletes dumps after 14 days. If this continues to be a problem, I could reduce the cleanup interval as well.

That puts scratch at the entirely-acceptable 63% and means the project share is now time :)

That was enough to clear the alerts, for sure.