Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

repository size not reduced after git filter-repo and moving files to lfs

Natalia
April 9, 2025

we did a git filter-repo to remove all large files from history and we moved some of the files to lfs (we see them there taking a little storage) and we don't see them in the branches anymore after the filter and push, but the repo size was not reduced online (repository settings).

i understand the gc is automatically run on cloud services.

what could be the issue? is there a way of telling what's going on?

 

thanks!

3 answers

1 vote
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 10, 2025

G'day, @Natalia 

Welcome to the community!

I have triggered GC on your repository and I can see that your total workspace consumption is now below the 1 GB limit.

As for @andydent I have triggered GC on the affected repository. The size of the repo is now at 300++ MB.

I hope this helps.

Regards,
Syahrul

Natalia
April 14, 2025

Thanks Syahrul! I have one more project I need to clean up and move some files to LFS. Is there a way to trigger the GC myself like committing some file or doing something that would trigger it? Or do I have to ask again for your help?

Thanks! 

Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 14, 2025

Hey @Natalia 

As per our page hereAfter you have rewritten the history, if the repository size is still over 75% of the size limit, we will automatically run garbage collection on your repository, which should reduce it to a manageable size. If that does not solve your repository size issue, you will need to let me know so we can manually trigger it.

Regards,
Syahrul

Natalia
November 6, 2025

@Syahrul  i'm still facing the same issue. I did a cleanup on  https://bitbucket.org/borealshift/rbwms/ and it still says over 200mb, after moving files to lfs. And the workspace is now over 1gb and readonly, and there was no gc triggered on its own. could you please trigger a gc? also for https://bitbucket.org/borealshift/quilmeswcs would be great.

Thanks!

Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 6, 2025

Hey @Natalia 

There were automatic GC triggers on the repository, but the size remains the same. I suspect that whatever cleanup you did was not applied correctly to the repository, so the size stays the same. Can you share with me what you did, the exact steps, and the command so I can get an idea?

Regards,
Syahrul

Natalia
November 7, 2025

Hi @Syahrul , the size of the repo was super high because there were large files (.APK) commited through history. We did something like


git lfs migrate import --include="*.apk" --everything
git lfs ls-files 
git push --all --force


its the same thing we did in the repo i asked to be gc a few months ago.
we did the same on the 2 i mentioned, and we also deleted a bunch of branches already merged. 

i see the apks in LFS in both repos, so that worked out. the rest is just code...

Like Syahrul likes this
Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 9, 2025

Hey @Natalia 

Is the current size as expected, since I can see that both repository sizes have been reduced?

Regards,
Syahrul

Natalia
November 10, 2025

Hi @Syahrul thanks for your patience. We found some apks that somehow escaped the lfs migrate so we did a git filter-repo --invert-paths --path  for each file manually.

could you please trigger the gc again for 
https://bitbucket.org/borealshift/rbwms/ 

https://bitbucket.org/borealshift/quilmeswcs

to see if that fixed the problem.

Thanks again!!!

Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 10, 2025

Hey @Natalia 

This is done! The repository size is now below 100 MB.

Regards,
Syahrul

Natalia
November 23, 2025

Hey @Syahrul  I really appreciate your help. 

We just finished deleting/moving all large files to LFS.

Could i ask you one last time to do a clean up on the last 3 repos so we know for sure what's our current situation before moving to a payed version?

the repos are:

https://bitbucket.org/borealshift/lindleyhuachipawcs

https://bitbucket.org/borealshift/lindleycentrowcs

https://bitbucket.org/borealshift/iqawcs

Thanks!

 

Syahrul
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 23, 2025

Hey @Natalia 

I have triggered GC on all 3 repositories.

Regards,
Syahrul

1 vote
Brant Schroeder
Community Champion
April 9, 2025

@Natalia welcome to the Atlassian community

Atlassian support will need to run garbage collection.  I have escalated this issue to them so they can take care of it for you.

andydent
April 9, 2025

I have the same problem @Brant Schroeder having cleaned up some very old big stuff on https://bitbucket.org/touchgram/touchgram using BFG

Seems as a free user I'm unable to contact support directly so would appreciate someone passing along my details to get that GC'd.

Happy to become paid user once I get monetisation up a bit to get past the spousal filter ;-)

Like Brant Schroeder likes this
0 votes
Natalia
November 6, 2025

sorry, wrong post.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events