Your workspace has exceeded the 1 GB limit

[amaurin]

Hello,

I'm unable to push to my repositories due to the following error:

"Your workspace has exceeded the 1 GB limit and has been placed in read-only mode. Learn more about upgrading your plan and checking storage usage."

However, this doesn't seem to match the actual usage. When I check the subscription details for my workspace, I see the following:

"0 MB of file storage used – 1 GB remaining"

I've only been using two repositories recently, and I'm confident they do not exceed the storage limit. I also haven't pushed any large files.

The warning in the UI is unclear, and it seems to contradict the information shown in the workspace settings.

Could you please clarify the situation?

[Mark C · Accepted solution]

Hi @amaurin

Welcome to the community.

If your workspace is on a Free plan, new limits will be enforced on May 29, 2025. For more details, please refer to the Blog.

The message: "0 MB of file storage used – 1 GB remaining"

Actually refers to your LFS storage limit, please note that repository size and LFS size are different. You can check our documentation here for more information.

Essentially, you're seeing 0 MB for LFS because you haven't uploaded any file to LFS yet.

Could you verify the message with the label "workspace storage" instead?

For example: "3 GB of workspace storage used"

Regards,
Mark C

[amaurin]

Thank you for your response. Yes, I’m on a free plan. I just deleted all my unused repositories (half of my repos) but still have the limit problem.

How is this limit calculated ? 

[Mark C]

Hi @amaurin

They're calculated based on the total repositories size in your workspace.

I actually checked all your repositories and I can see that they're indeed accumulating 3.3 GB space.

To proceed further, you can also consider the following options:

Option 1 - Delete & recreate the repositories
This is the fastest way to solve the problem, but loses metadata such as PRs, Pipelines, Permissions, etc.

1. Perform a clone of those repositories for backup purposes

2. Delete those repositories from your workspace to free up space and allow you to push. NOTE: This will permanently remove metadata such as PR's/pipelines/user permissions etc.

3. Identify the largest files in your repositories by executing the following command:
   git rev-list --objects --all \
   | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \| awk '/^blob/ {print substr($0,6)}' \
   | sort -r --numeric-sort --key=2 \
   | numfmt --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest

4. Perform cleanup operations locally to reduce the size

5. Once complete, push those repositories back to your workspace by creating a blank repository with the same name of the deleted repository, then mirror pushing the contents of the cleaned repository:

HTTPS
git push --mirror https://<username>@bitbucket.org/<WorkspaceID>/<RepoName>.git
SSH
git push --mirror git@bitbucket.org:<WorkspaceID>/<RepoName>.git

NOTE: This will remove metadata such as PR's/pipelines/permissions etc but will keep your commit history and binary files intact.

Option 2 - Temporarily upgrade

1. Upgrade to a paid plan and utilise our 30-day trial period to restore functionality and provide more time to reduce your repository directly without deletion. You can choose to continue or cease your trial before the end of the 30-day period.

2. If you encounter any issues during this period - you may raise a ticket directly with our support team using your workspace URL: Atlassian Support  

Please let me know how this goes.

Regards,
Mark C

[amaurin]

thanks for your responses.