This page provides troubleshooting information to help address issues you mightencounter while attempting to create a Filestore instance.

PERMISSION DENIED when creating a Filestore instance

1. Check if the Filestore API is enabled:

   gcloud services enable file.googleapis.com

2. Each Filestore instance must have an IP address range associatedwith it that does not overlap with another range in use. For a detailed listof restrictions, seeConfiguring a reserved IP address range.

3. Check if you have theroles/file.editor role. For details seeAccess control orIAM roles and permissions.

4. If you are still encountering the error, then the Filestoreservice account might have had itsfile.serviceAgent role removed. To check if this is the case, run:

     gcloud projects get-iam-policyproject-id-or-number \        --flatten="bindings[].members" \        --format='table(bindings.role)' \        --filter="bindings.members:service-project-number@cloud-filer.iam.gserviceaccount.com"

   where:

   • project-id-or-number is the ID or number of your Google Cloudproject.
   • project-number is the number of your Google Cloudproject.

   The command should return something similar to the following:

   ROLEroles/file.serviceAgent

   Ifroles/file.serviceAgent is not listed, you can restore it by running:

     gcloud projects add-iam-policy-bindingproject-id-or-number  \      --member serviceAccount:service-project-number@cloud-filer.iam.gserviceaccount.com  \      --role roles/file.serviceAgent

System limit for internal resources has been reached error when creating an instance

This error is caused by Filestore reaching an internal networkquota. For every VPC network that you create a Filestore instanceon, Filestore must create aninternal networkthat peers with that network. These internal networks are preserved evenwhen the Filestore instances and VPC networks associated with themare deleted.

Once the number of internal networks reaches 49 for a project,Filestore is no longer able to create new internal networks, whichprevents you from creating Filestore instances on new VPC networks.Attempting to do so results in one of the following errors:

System limit for internal resources has been reached. Please request to adjust limit here: https://forms.gle/PFPJ2QD4KnCHzYEx9

You can clear the internal networks by disabling and then re-enabling theFilestore API.

Use thegcloud services disablecommand to disable the Filestore API:

gcloud services disable file.googleapis.com

Then, use thegcloud services enablecommand to re-enable the Filestore API:

gcloud services enable file.googleapis.com

If you can't disable the API because you have Filestore instancesthat you cannot delete or you don't want to lose quota that you've been grantedthrough quota increase requests, then you can fill out the following form tohave your network limits adjusted:

https://forms.gle/PFPJ2QD4KnCHzYEx9

If you need to regularly delete and create VPC networks andFilestore instances, there are two ways to avoid running out ofnetwork quota:

• When you create a VPC network, use the same name as a previous network that'sbeen used for Filestore instance creation.

• Cycle through a pool of no more than 49 VPC networks instead of deleting andthen recreating them.

What's next

• Known issues
• Troubleshoot slow performance