The following table describes resource limits for Cloud Volumes Service:
|Resource||Default limit for CVS||Default limit for CVS-Performance|
|Number of snapshots per volume||255||255|
|Number of subnets delegated to Cloud Volumes Service for Google Cloud per VPC network||1||1|
|Number of VPC networks per project||5||5|
|Minimum size of a single volume||1024 GiB||1024 GiB|
|Maximum size of a single volume||100 TiB||100 TiB|
|Maximum size of a single file||16 TiB||16 TiB|
|Maximum size of a single directory||2.8 million files||3.4 million files|
|Maximum number of files (maxfiles) per volume||21.2 million||100 million|
|Maximum number of volumes per project||100 per zone||100 per region|
|Maximum number of NFS export rules per volume||5||5|
|Number of backups per volume||32||Not supported|
Cloud volumes have a limit called maxfiles. The maxfiles limit is the number of files a volume can contain. The maxfiles limit for a volume is indexed based on the size (quota) of the volume. The maxfiles limit for a volume increases or decreases at the rate of 20 million files per TiB of provisioned volume size.
The service dynamically adjusts the maxfiles limit for a volume based on its provisioned size. For example, a volume configured initially with a size of 1 TiB would have a maxfiles limit of 20 million. Subsequent changes to the size of the volume would result in an automatic readjustment of the maxfiles limit based on the following rules:
|Volume size (quota)||Automatic readjustment of the maxfiles limit|
|< 1 TiB||20 million|
|≥ 1 TiB but < 2 TiB||40 million|
|≥ 2 TiB but < 3 TiB||60 million|
|≥ 3 TiB but < 4 TiB||80 million|
|≥ 4 TiB||100 million|
For any volume size, you can initiate a support request to increase the maxfiles limit beyond 100 million.
For volume provisioning failures with a "Not enough ILB resources" error, you can Create a support case with NetApp to request an increase to the limit of ILB forwarding rules for your project.