配额用于指定您可以使用的可计数共享资源的数量。配额由 Google Cloud NetApp Volumes 等 Google Cloud 服务定义。
系统限制是无法更改的固定值。
Google Cloud 使用配额来帮助确保公平性并减少资源使用和可用性的激增。配额用于限制您的 Google Cloud 项目可使用的Google Cloud 资源的数量。配额适用于一系列资源类型，包括硬件、软件和网络组件。例如，配额可以限制对某项服务的 API 调用次数、您的项目并发使用的负载均衡器数量或者您可以创建的项目数量。配额可以防止服务过载，从而保护Google Cloud 用户社区。配额还可以帮助您管理自己的 Google Cloud 资源。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[],[],null,["# Quotas and limits\n\nThis document lists the quotas and system limits that apply to\nGoogle Cloud NetApp Volumes.\n\n- *Quotas* specify the amount of a countable, shared resource that you can use. Quotas are defined by Google Cloud services such as Google Cloud NetApp Volumes.\n- *System limits* are fixed values that cannot be changed.\n\nGoogle Cloud uses quotas to help ensure fairness and reduce\nspikes in resource use and availability. A quota restricts how much of a\nGoogle Cloud resource your Google Cloud project can use. Quotas\napply to a range of resource types, including hardware, software, and network\ncomponents. For example, quotas can restrict the number of API calls to a\nservice, the number of load balancers used concurrently by your project, or the\nnumber of projects that you can create. Quotas protect the community of\nGoogle Cloud users by preventing the overloading of services. Quotas also\nhelp you to manage your own Google Cloud resources.\n\nThe Cloud Quotas system does the following:\n\n- Monitors your consumption of Google Cloud products and services\n- Restricts your consumption of those resources\n- Provides a way to [request changes to the quota value](/docs/quotas/help/request_increase) and [automate quota adjustments](/docs/quotas/quota-adjuster)\n\nIn most cases, when you attempt to consume more of a resource than its quota\nallows, the system blocks access to the resource, and the task that\nyou're trying to perform fails.\n\nQuotas generally apply at the Google Cloud project\nlevel. Your use of a resource in one project doesn't affect\nyour available quota in another project. Within a Google Cloud project, quotas\nare shared across all applications and IP addresses.\n\n\nThere are also *system limits* on NetApp Volumes resources.\nSystem limits can't be changed.\n\nGoogle Cloud NetApp Volumes use is subject to limits and default quotas. Limits\ncan't be changed, however, you can request a quota increase. To learn more,\nsee [Request a quota increase](/netapp/volumes/docs/quotas#request_a_quota_increase).\n\nView your API quotas\n--------------------\n\nView your API quotas and usage for NetApp Volumes in the\nGoogle Cloud console.\n\n[Go to NetApp API quotas](https://console.cloud.google.com/apis/api/netapp.googleapis.com/quotas)\n\nNetApp Volumes default quotas\n-----------------------------\n\nThe following table shows the default quotas for each resource. To increase or\ndecrease most quotas, use the Google Cloud console. For more information, see\n[Request a higher quota limit](/docs/quotas/help/request_increase).\n\nNetApp Volumes limits\n---------------------\n\nNetApp Volumes feature limits vary by location and region. The\nfollowing tables show the current limits per resource. You cannot change\nthese limits.\n\n### Backup limits\n\n### Storage pool limits\n\n### Networking limits\n\n### Volume limits\n\n### Network File System (NFS) limits\n\n### Active Directory policy limits\n\n### Inode limits\n\nEvery directory, file, or link uses an inode, but each volume has a limit on how\nmany inodes it can store. If that limit is reached, you can't create new files\nor directories, even if there is free space. To resolve this, you must delete\nexisting files or directories to free up inodes. Alternatively, you can also\nincrease the volume capacity to add more inodes.\n\nGoogle Cloud NetApp Volumes allocates one inode for every 32 KB of volume\ncapacity, based on an average file size of 32 KB. If your average file size\nis smaller, you might run out of inodes before using up all the available\nstorage capacity.\n\nVolumes in Standard, Premium, and Extreme service levels provide a minimum of\n21.2 million inodes for each volume. Beyond 683 GiB of capacity, the inode\ncount increases linearly with volume capacity, adding one inode for every\n32 KB. Flex volumes start with approximately 31,000 inodes for a 1 GiB\nvolume and grow linearly with volume capacity at one inode for every 32 KB.\n\nAuto-tiering reduces the amount of hot data in a volume, but doesn't impact the\nnumber of used inodes.\n\nThe maximum hard limit for each volume is 2,040 million inodes.\n\nThe following table provides a few examples of volume capacity versus maximum\ninodes for volumes:\n\nFor more information about monitoring inode usage, see\n[Methods for monitoring volume usage](/netapp/volumes/docs/monitor/monitor-volume-usage#methods_for_monitoring_volume_usage).\n\nRequest a quota increase\n------------------------\n\nTo adjust most quotas, use the Google Cloud console.\nFor more information, see\n[Request a quota adjustment](/docs/quotas/help/request_increase)."]]
