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 size not reduced after git filter-repo and moving files to lfs

Natalia

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!

Accepted answers

All comments

Brant Schroeder

@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

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 ;-)

Syahrul

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

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

Hey @Natalia

As per our page here, After 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

sorry, wrong post.

Natalia

@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!

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