Forums

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

Workspace "maruen" stuck in read-only mode after reducing repository size

maruen
August 7, 2026
My Bitbucket Cloud workspace "maruen" (Free plan) has been placed in
read-only mode for exceeding the 1 GB repository storage limit, and all
pushes are rejected by the pre-receive hook.
I have already reduced the size:
- The oversized repository was "maruen/docker" (~600 MB). Its history
contained two large data files that had been committed by mistake.
- I removed them with git filter-repo, taking the repository from 601 MB
to 346 MB, with no single file over 100 MB.
- I then deleted the "maruen/docker" repository entirely and re-created it
empty, intending to push the slimmed history.
My remaining repositories total well under 1 GB (roughly 540 MB in total:
docker 346 MB, kinesis-event-producer 140 MB, olympus-file-parser 53 MB,
and several repositories under 1 MB each).
Despite this, the workspace has remained in read-only mode for over a day
and pushes are still rejected with "This workspace is over the 1 GB size
limit". It appears the storage figure has not been recalculated after the
deletion.
Could you please run garbage collection on the workspace so the storage
usage is recalculated and read-only mode is lifted?
Thank you.

1 answer

0 votes
Tomislav Tobijas
Community Champion
August 7, 2026

Hi @maruen ,

I've pinged the forum support team to take a look at this. 👀
Someone should get back to you here in 1-2 business days.

Cheers,
Tobi

maruen
August 7, 2026

Thanks @Tomislav Tobijas, looking forward to it.

Like Tomislav Tobijas likes this

Suggest an answer

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

Atlassian Community Events