Repo size warning still get displayed after cleanup & push with BFG

Question

Hi,

I have a large repo size with almost 2.02 GB, so I have duplicated it to another temp repo to test the BFG cleaner on it before using the BFG on the original repo, after following the BFG documentation, and ran all the needed commands, then pushing the decreased sized repo(415MB) to the remote repo, the repo size became 2.15 GB.

So, please run a git gc on the remote to clean up the server.  Thank you!

Theodora Boudale · Answer

Hi @Mahmoud Jorban,

Thank you for the info. I ran another git gc for the repo, but its size remains 2.1 GB.

I went ahead and created a support ticket for you so we can investigate this further, using the email of your community account.

You should have received an email with a link to the support ticket. Just in case you haven't received it, please feel free to let me know and I can post the ticket URL here. The ticket will be visible only to you and Atlassian staff, no one else can view its contents even if they have the URL.

If you have any questions, please feel free to let me know.

Kind regards,
Theodora

Mahmoud Jorban · Answer

Hi @Theodora Boudale ,

Regarding the first point, after running the command, I get the following:

count: 0
size: 0 bytes
in-pack: 324456
packs: 1
size-pack: 380.59 MiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

And regarding the second point, yes, I ran that command, and I followed the same instructions in the BFG official doc page here, under the usage section.

And regarding the third point, yes, I pushed my changes to the repo whose name ends with _temp.

Theodora Boudale · Answer

Hi @Mahmoud Jorban,

I can see in our system that your Bitbucket Cloud account has access to 2 repos with a size of around 2 GB. I believe that the temp repo is the one whose name has _temp in the end? I ran a git gc for this repo, but its size remains 2.1 GB.

Could you please let me know:

1. What is the output of the command git count-objects -Hv in your local mirror clone where you ran BFG?

2. Did you run the following command in that mirror clone prior after you executed BFG and prior to pushing?

git reflog expire --expire=now --all && git gc --prune=now --aggressive

3. Could you please confirm if you pushed your changes to the Bitbucket repo whose name ends in _temp?

Kind regards,
Theodora