Repository size of mirror bigger than repository size

[alexanderadam]

• Gitea version (or commit ref): 1.12.6 built with GNU Make 4.2.1, go1.14.12 : bindata, sqlite, sqlite_unlock_notify
• postgres

Description

I admit that I have barely have data now but I saw that I had a mirrored repository that was much bigger than the original repository. I deleted the repository and recreated the mirror and now the size is as expected.
It didn't have any additional branches, forks, wiki or assets. It was really just a mirrored repository. Also Prune was activated in Mirror Settings.

Do you have any idea what might have caused this, how to fix it or how I could get some additional data in retrospect?

[lunny]

Are there also archivers which stored under the repository. I think It depends on have you download archivers.

[alexanderadam]

It depends on have you download archivers.

I don't know what this means but I didn't do anything except of using the regular mirror functionality.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

[99rgosse]

I've got the same issue on a Gitea 1.14.6 with huge data.
My migrated repository (with lots of LFS files) is about 9Gb and Gitea shows 14Gb, the original repo on Gitlab is 4.5 Gb.

I tried Garbage collection and check repository statistic tasks, but nothing for the moment.
(Garbage Collection seems not to go through all, but as my data are really huge, I think it needs some more time...)