nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Repository is not over the size limit

Dana Adriana Zainescu

It says it has 1.13 GiB, but then it says repository is over the size limit (2 GB) and will not accept further additions:

Enumerating objects: 25046, done.
Counting objects: 100% (25046/25046), done.
Delta compression using up to 4 threads
Compressing objects: 100% (17794/17794), done.
Writing objects: 100% (25046/25046), 1.13 GiB | 8.51 MiB/s, done.
Total 25046 (delta 7237), reused 24962 (delta 7170)
remote: Resolving deltas: 100% (7237/7237), done.
remote: Checking connectivity: 43, done.
remote: Repository is over the size limit (2 GB) and will not accept further additions.
remote: 
remote: Learn how to reduce your repository size: https://confluence.atlassian.com/x/xgMvEw.
To bitbucket.org:geopost/<repo>.git
! [remote rejected] master-live -> master-live (pre-receive hook declined)
error: failed to push some refs to 'git@bitbucket.org:geopost/<repo>.git'

I've also tried to find the site of the repo with:

git gc
git count-objects -vH

And it also says:

size-pack: 1.13 GiB

On the other hand, as an example, we have another repo that is 2.21GB and commits still work fine there.

EDIT: I tried creating and deleting a branch, as it was suggested online and commits work now. It says Repository details: Size1.9 GB on Bitbucket.
Any idea how can I get it down to 1.13 GB, as git tells me this is the actual size of the repo?

Accepted answers

Daniil Penkin

Hello @Dana Adriana Zainescu,

This is very likely due to the fact that Git garbage collection is not triggered on every repository update as it is an expensive operation. This is why one of the steps in the guide Mike mentioned above is to request our Support team to run GC.

Eventually it would've been triggered automatically, but for now I forced GC in four repositories under the account you mentioned that matched the size you mentioned and last access date (since you didn't specify exact repo in question). All repositories reduced in size to 1.1-1.3 GB. Please let me know if I guessed the right repo.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil

All comments

Mike Howells

Please refer to the guide to reducing repo size mentioned in the error message for information on the size limits and instructions on getting down below the 2GB limit.

You may have to request technical support to get your repo below the 2GB limit. You can ask the support engineer why your 2.21GB repo is not affected by the limit.

Once below the limit, the guide to maintaining git repos explains how to remove other large files from your repo.

Apologies for your confusing experience. We are currently investigating some issues with the way repo sizes are calculated. This is a tricky area that has a big performance impact so we're being very cautious, rolling out changes progressively and monitoring their effects carefully.

Daniil Penkin

Hello @Dana Adriana Zainescu,

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil

Dana Adriana Zainescu

Thanks for the information. Will have a look over those links!

Dana Adriana Zainescu

Thanks, Daniil.
Have you also done this for dpd.co.uk? Git is telling me it has 2.21 GiB, instead of the 4.6 GB on Bitbucket. Can you have a look please? And I'll also try to reduce the size a bit more after that.
Also, I suppose there's no way of actually increasing the space limit for the repo? As it's a bit hard to restrict commits, since they're sent from the Alfresco WCM host serving the live website.

Daniil Penkin

No worries.

Have you also done this for dpd.co.uk?

Done just now, Bitbucket is showing 2.3 GB now.

Also, I suppose there's no way of actually increasing the space limit for the repo?

No, unfortunately this one is carved in stone. This is mainly due to the potential performance issues that Git has with larger repositories. There are a couple workarounds for this though: you can make use of Git LFS for large files or split the repo history like it is described in this Git guide chapter. Both ways aren't trivial and might not be easily applicable in your case.

Cheers,
Daniil

Dana Adriana Zainescu

I see, thanks for the help.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

git

repository