Repo Size Constraints & Read Only

Brad Aytes

I have migrated a SVN repo to GIT using the Atlassian tool 'svn-migration-scripts.jar' & 'git svn'. Our SVN repo is around 39GB, and migrated to GIT is the same.

 

I was finally able to get it uploaded up to our bitbucket account (premium account) & i was able to clone the remote repo locally, then when i go to add a file to the repo and push it up its giving the typical: "remote: Repositiory is in read only mod (over 2 GB size limit)....."

 

I've tried 'git reset --hard HEAD~1' then a 'git push --force'. I've tried everything in the links below, everything to get the repo out of read only mode and actually get things working properly to be able to get the rest of our development team switched over to using GIT. 

 

Currently I'm trying to run 'gitextentions' "Find Large Files" to remove some of the things that *CAN* be removed from the repository to try and shrink it down as much as possible however i know that it is going to be impossible to shrink 39GB down to under 2GB.

 

What options do i have to get this repo out of read only mode and working properly?

I know this has been discussed several times.

(ref: https://community.atlassian.com/t5/Bitbucket-questions/This-repository-reached-the-2-GB-limit-restricting-it-to-read/qaq-p/689097

ref: https://community.atlassian.com/t5/Bitbucket-questions/How-to-push-in-read-only-mode/qaq-p/616817

etc)

Any help is GREATLY appreciated.

 

Cheers,

 

Brad

Ana Retamal

 

Hi Brad, welcome to the Community!

The 2GB limitation can not be lifted, the repo needs to be smaller than 2GB, otherwise you'll be in read-only mode. With this said, let's try to find a solution

git reset --hard HEAD~1 will not help in your case. What that command does is to reset back 1 commit to bring the repo back to the size it was at the time of that commit. In your case this will not help because your repo most likely was already 39GB one commit ago. This is further explained in the article Reduce repository size. What you'd need to do is to reset back as many commits as necessary so your repo goes back to under 2GB. I don't think this will be possible for you. 

You'll need what's taking up so much space in your repository. Do you have binaries and images? If so, Git is not a good candidate for them. Our recommendation would be to use Git LFS (here are some instructions on how to use this with Bitbucket, too) or store them separately so they are not part of your repo. 

Hope that helps! Let us know if you have any questions, Brad.

Kind regards,

Ana