Repository archives balooned to take up all space on disk

[infogulch]

This happened again today. 48+GB of actually useless "repository archives" whatever that means. ~~Even login fails when the disk is full so I can't even log in to fix it. ~~ I was able to log in finally.

Is there a way to set disk quotas for apps so when they misbehave the whole cloudron doesn't go belly up? Sigh.

[infogulch]

So I don't know what "repository archives" are, what they're for, why they take up literally 12x the storage of the actual repository data, why clicking this button fixes it, and why that has no effect on the operation of the site.

[robi]

@infogulch perhaps because of the frequency of the sync and the versioning of each sync?

[infogulch]

Yeah it probably has to do with the Update Mirrors cron task that runs every 10m, since that's the only activity on the server. I did notice that the Update Mirrors task run count was about 280 in both cases. Maybe a recent update is now leaving junk behind when it updates mirrors that isn't being cleaned up.

[nebulon]

So this is the default behavior to create new archive files and not something you have enabled?

[robi]

Would https://github.com/pojntfx/octarchive be better?

[infogulch]

Yeah that seems to be the issue:

It's currently at 30GB (was 30MB 19 hours ago), exactly:

31069204

Then I ran the "Update Mirrors" task, now it's:

31733536

[mario]

It appears this issue started happening as of most recent gitea update.

[robi]

@mario look for a new "feature" that does this "for you"

[mario]

@robi features are great

[infogulch]

Release 1.20.0 included these PRs related to mirroring, maybe one of them caused the issue:

• Refactor Pull Mirror and fix out-of-sync bugs #24732
• Use the type RefName for all the needed places and fix pull mirror sync bugs #24634
• Allow skipping forks and mirrors from being indexed #23187