Cannot Restore Write Access to Repository (2 GB Limit Overshot)

I recently got the following warning on my repository

This repository reached the 2 GB limit, restricting it to read-only access.

I then followed the instruction given here to reduce my repository size and restore write access.

I ran the following commands in my corresponding local git repo (which was up-to-date with this one) and ran:

git reset --hard <commit-SHA>

git push --force origin master

The first command executed correctly and took me to a commit which I had successfully pushed before, and which was under the 2 GB limit. But the second command gives me the error:

remote: abort: repository is in read only mode (over 2 GB size limit). Learn how to reduce your repository size:
fatal: unable to access '': The requested URL returned error: 403

If I can't force push the reduced repository back, how am I to resolve this issue?

Could someone help me resolve this issue, please?

It is very urgent for me...this is part of a recruitment test which I have to complete tomorrow.



1 answer

0 vote

Hi Rishabh, can you try force push again using the Bitbucket account that is the owner of the repository?

I've checked your  remote repository and the size was 9GB. I've run an aggressive gc and the size has decreased to 2.5GB, which means you'll need to reduce the size of your repository a bit more. Please run this command and show us the output so we can also see the size of your local repo.

I've also checked your repository's files and realized that you have a large number of binaries, which are not good candidates for being stored in DVCS systems. For binary or executable storage we recommend you to enable LFS (Large File Storage), or consider another file hosting services  such as DropBox, rsync, rsnapshot, rdiff-backup, and so forth.

Let us know if you need any further assistance!

Best regards,


Hey sorry...I wasn't working on this repository for the past week.


But yes, I got rid of all of the binary files and other unnecessary junk. I've been able to force push and I'm pretty sure the size is well below 2GB right now.

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

708 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot