If I exceed the storage limit of 10 GB in one project, is it normal to lose the ability to commit/push to my other projects as well?
Situation:
I am using the Free Plan.
I have the following messages in my account:
This namespace contains locked projects
You have reached the free storage limit of 10.0GiB on 1 project. To unlock them, please purchase additional storage.
You have reached the free storage limit of 10 GB on 1 project. To unlock it, please purchase additional storage
Please purchase additional storage to unlock your projects over the free 10 GB project limit. You can’t push to your repository, create pipelines, create issues or add comments. To reduce storage capacity, delete unused repositories, artifacts, wikis, issues, and pipelines.
There is a project X that has gone over the 10GB limit ( Usage: 13.9GB, Excess Usage: 3.9GB) which I understand is the locked project.
However, I have several other projects in my account which are way below the 10GB limit; but any attempt to push to any of them results in the following error message:
remote: GitLab: Your push to this repository would cause it to exceed the size limit of 10 GB so it has been rejected. Please contact your GitLab administrator for more information.
Does this mean by exceeding the storage limit of 10 GB in project X, I have lost the ability to commit/push to my other projects as well?
Same issue since today. Removed an unused but excess size repo but still unable to push anything to owned by the group.
/usage_quotas#storage-quota-tab shows that the problematic repo still exists but it’s already 404. Had to change project ownership to another group for now for push to work.
@Ragnar seems like having a similar issue. But its is none of my projects.
It seems that this is related to the community forks i am member of for some time now.
Can you please have a look and tell me what to do?! Maybe raise the limit for my user
as i’m doing some work on gitlab.
I think it’s probably not the same bug since we haven’t had reports of this for 3 years.
I’m trying to better understand your situation, are you blocked on pushing to ALL of your projects or just the one that’s above the limit?
Also if you are comfortable sharing in public can you link me which project it is?
Otherwise I can raise a support issue on your behalf and we can have the conversation be more private
If that’s the case it’s obviously not OK that GitLab forking your community contribution is blowing up the limit I’m chasing down some leads internally (might take me a few days) and if they do not pan out I’ll open a support ticket on your behalf.
If you get tired of waiting for me you can raise a support ticket yourself
The problematic project seems to be your fork of GitLab.org / GitLab · GitLab - there are cost factors applied to the project and the banner and blocking behaviour is misleading. There’s planned work in the future to improve on this.
The problem should not be the TYPO3 project. You can verify this by looking at the project fork storage usage
It’s not a great experience as a community contributor to be hit by storage limits when forking the GitLab repo like this. There’s a more detailed write-up in this blog post
To alleviate this experience we now recommend to use the GitLab Community Fork when working on GitLab projects.
Apologies this took to long to figure out and that you ended up being blocked like this. I hope the links I’ve shared give you a clear path forward. Otherwise let me know and I’ll see what I can do to help
