diff options
Diffstat (limited to 'doc/user/usage_quotas.md')
| -rw-r--r-- | doc/user/usage_quotas.md | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/doc/user/usage_quotas.md b/doc/user/usage_quotas.md index 0740108a168..822f169c2a3 100644 --- a/doc/user/usage_quotas.md +++ b/doc/user/usage_quotas.md @@ -76,8 +76,8 @@ Depending on your role, to manage your transfer usage you can [reduce Container Projects on GitLab SaaS have a 10 GB storage limit on their Git repository and LFS storage. After namespace-level storage limits are applied, the project limit is removed. A namespace has either a namespace-level storage limit or a project-level storage limit, but not both. -When a project's repository and LFS reaches the quota, the project is locked. -You cannot push changes to a locked project. To monitor the size of each +When a project's repository and LFS reaches the quota, the project is set to a read-only state. +You cannot push changes to a read-only project. To monitor the size of each repository in a namespace, including a breakdown for each project, [view storage usage](#view-storage-usage). To allow a project's repository and LFS to exceed the free quota you must purchase additional storage. For more details, see [Excess storage usage](#excess-storage-usage). @@ -85,45 +85,45 @@ you must purchase additional storage. For more details, see [Excess storage usag ### Excess storage usage Excess storage usage is the amount that a project's repository and LFS exceeds the [project storage limit](#project-storage-limit). If no -purchased storage is available the project is locked. You cannot push changes to a locked project. -To unlock a project you must [purchase more storage](../subscriptions/gitlab_com/index.md#purchase-more-storage-and-transfer) -for the namespace. When the purchase is completed, locked projects are automatically unlocked. The +purchased storage is available the project is set to a read-only state. You cannot push changes to a read-only project. +To remove the read-only state you must [purchase more storage](../subscriptions/gitlab_com/index.md#purchase-more-storage-and-transfer) +for the namespace. When the purchase is completed, read-only projects are automatically restored to their standard state. The amount of purchased storage available must always be greater than zero. The **Storage** tab of the **Usage Quotas** page warns you of the following: - Purchased storage available is running low. -- Projects that are at risk of being locked if purchased storage available is zero. -- Projects that are locked because purchased storage available is zero. Locked projects are +- Projects that are at risk of becoming read-only if purchased storage available is zero. +- Projects that are read-only because purchased storage available is zero. Read-only projects are marked with an information icon (**{information-o}**) beside their name. #### Excess storage example The following example describes an excess storage scenario for a namespace: -| Repository | Storage used | Excess storage | Quota | Status | -|------------|--------------|----------------|--------|-------------------| -| Red | 10 GB | 0 GB | 10 GB | Locked **{lock}** | -| Blue | 8 GB | 0 GB | 10 GB | Not locked | -| Green | 10 GB | 0 GB | 10 GB | Locked **{lock}** | -| Yellow | 2 GB | 0 GB | 10 GB | Not locked | -| **Totals** | **30 GB** | **0 GB** | - | - | +| Repository | Storage used | Excess storage | Quota | Status | +|------------|--------------|----------------|--------|----------------------| +| Red | 10 GB | 0 GB | 10 GB | Read-only **{lock}** | +| Blue | 8 GB | 0 GB | 10 GB | Not read-only | +| Green | 10 GB | 0 GB | 10 GB | Read-only **{lock}** | +| Yellow | 2 GB | 0 GB | 10 GB | Not read-only | +| **Totals** | **30 GB** | **0 GB** | - | - | -The Red and Green projects are locked because their repositories and LFS have reached the quota. In this +The Red and Green projects are read-only because their repositories and LFS have reached the quota. In this example, no additional storage has yet been purchased. -To unlock the Red and Green projects, 50 GB additional storage is purchased. +To remove the read-only state from the Red and Green projects, 50 GB additional storage is purchased. Assuming the Green and Red projects' repositories and LFS grow past the 10 GB quota, the purchased storage -available decreases. All projects remain unlocked because 40 GB purchased storage is available: +available decreases. All projects remain read-only because 40 GB purchased storage is available: 50 GB (purchased storage) - 10 GB (total excess storage used). | Repository | Storage used | Excess storage | Quota | Status | |------------|--------------|----------------|---------|-------------------| -| Red | 15 GB | 5 GB | 10 GB | Not locked | -| Blue | 14 GB | 4 GB | 10 GB | Not locked | -| Green | 11 GB | 1 GB | 10 GB | Not locked | -| Yellow | 5 GB | 0 GB | 10 GB | Not locked | +| Red | 15 GB | 5 GB | 10 GB | Not read-only | +| Blue | 14 GB | 4 GB | 10 GB | Not read-only | +| Green | 11 GB | 1 GB | 10 GB | Not read-only | +| Yellow | 5 GB | 0 GB | 10 GB | Not read-only | | **Totals** | **45 GB** | **10 GB** | - | - | ## Namespace storage limit |