Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

After switching to LFS I still see the warning


My repo includes quite a large amount of *.lib files  which consume space. Lately I started to see a warning about excessive repo size and decided to switch to LFS. I've followed instructions at and successfully converted all large binaries to references to storage provided by Bitbucket itself.

Here is the final command result:

> ~/tmp/splitcam.git% git push --force

Uploading LFS objects: 100% (297/297), 5.8 GB | 0 B/s, done.                                                                                                                        

Enumerating objects: 11495, done.

Counting objects: 100% (11319/11319), done.

Delta compression using up to 16 threads

Compressing objects: 100% (4802/4802), done.

Writing objects: 100% (11107/11107), 9.08 MiB | 2.86 MiB/s, done.

Total 11107 (delta 7497), reused 8430 (delta 6258)

remote: Resolving deltas: 100% (7497/7497), completed with 136 local objects.

remote: WARNING Repository size in Bitbucket is currently 1.6 GB

remote: Above the 2 GB size limit further commits are rejected

remote: Reduce repository size by removing large files from history

remote: HINT Learn how to reduce repository size:


 + 3d5ecd7...ee08eaf devel -> devel (forced update)

 + c37371a...5bcb133 master -> master (forced update)

 + 2bb36cb...5fdbd78 pip -> pip (forced update)

 + 6becc9b...71af10a toto -> toto (forced update)

 + 3d5ecd7...ee08eaf vcapture -> vcapture (forced update)

 + f60a5fc...cfe90c9 vit -> vit (forced update)

 + e2af7fb...0387d55 v10.0.43 -> v10.0.43 (forced update)


So I still continue receiving these warnings about large repo size. The same warning is displayed in browser user interface on Bitbucket web site.

If I clone the repo I can clearly see that the large binaries are now replaced with their references to LFS objects, like this:

[content of opencv_ts411.lib as an example]

oid sha256:d073d0e9375be17881919235cad115628a12ed22310e113b377ff85dc232293b
size 9891348

I wonder why it says the file is located at

What am I doing wrong and why my repo size was not changed?

Thank you for reading this far!

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

875 views 16 11
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you