Codeberg/Community
54
325
Fork
You've already forked Community
12

Snowflake storage quota exceeded, but no documentation on what that means #1980

Closed
opened 2025年06月11日 08:37:55 +02:00 by artifechs · 3 comments

Comment

We're using Codeberg to host a game project with almost all binary files listed in LFS instead of the main repo. The total size of my local folder is 1.3GB.

When I go to our organisation's storage quota page, it says that "snowflake" storage is exceeded at 1.5GB/750MB. I cannot find any information on what "snowflake" means in this context.

So I'm confused, does this mean I can't store this amount of binary files on Codeberg after all, even though LFS is supported?

### Comment We're using Codeberg to host a game project with almost all binary files listed in LFS instead of the main repo. The total size of my local folder is 1.3GB. When I go to our organisation's storage quota page, it says that "snowflake" storage is exceeded at 1.5GB/750MB. I cannot find any information on what "snowflake" means in this context. So I'm confused, does this mean I can't store this amount of binary files on Codeberg after all, even though LFS is supported?

Hello,

I also have exceeded my snowflake quota (2.8GB/750MB). It seems that the root cause is this repository that displays a 2.8GB use of LFS.

But I am not using Git LFS for my repository (check my workflow here) and I am force-pushing every time so that the output repository always has 1 commit.

Could someone help me?

Hello, I also have exceeded my snowflake quota (2.8GB/750MB). It seems that the root cause is [this repository](https://codeberg.org/lfavole/flashcards-site) that displays a 2.8GB use of LFS. But I am not using Git LFS for my repository ([check my workflow here](https://codeberg.org/lfavole/flashcards/src/commit/9c450aa8/.forgejo/workflows/build.yml)) and I am force-pushing every time so that the output repository always has 1 commit. Could someone help me?

You can see the meaning of the different storage names in the latest blog post here: https://blog.codeberg.org/letter-from-codeberg-we-love-our-new-infrastructure.html

It seems the plan is to make these distinctions clearer going forward :)

@lfavole the display of the storage use depends on git's garbage collect having run. Iirc Codeberg runs it around once a day, so the larger total might be a result of that. If it talks about the snowflake quota it should also not be the LFS :)

You can see the meaning of the different storage names in the latest blog post here: https://blog.codeberg.org/letter-from-codeberg-we-love-our-new-infrastructure.html It seems the plan is to make these distinctions clearer going forward :) @lfavole the display of the storage use depends on git's garbage collect having run. Iirc Codeberg runs it around once a day, so the larger total might be a result of that. If it talks about the snowflake quota it should also not be the LFS :)

@gedankenstuecke thanks! I guess I need to contact Codeberg directly to get a higher quota

@gedankenstuecke thanks! I guess I need to contact Codeberg directly to get a higher quota
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1980
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?