[[["易于理解","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-18。"],[[["\u003cp\u003eThis page offers guidance on resolving common issues encountered when creating Filestore instances, specifically addressing \u003ccode\u003ePERMISSION DENIED\u003c/code\u003e and \u003ccode\u003eSystem limit for internal resources has been reached\u003c/code\u003e errors.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve \u003ccode\u003ePERMISSION DENIED\u003c/code\u003e, ensure the Filestore API is enabled, an appropriate IP address range is configured, and you have the necessary \u003ccode\u003eroles/file.editor\u003c/code\u003e role.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePERMISSION DENIED\u003c/code\u003e error can also occur if the Filestore service account's \u003ccode\u003efile.serviceAgent\u003c/code\u003e role was removed, and instructions are given on how to check and re-add it.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eSystem limit for internal resources has been reached\u003c/code\u003e error is caused by exceeding the internal network quota limit of 49, and can be fixed by disabling and re-enabling the Filestore API, but caution is advised as this will delete the quota increase requests.\u003c/p\u003e\n"],["\u003cp\u003eIf you can not disable the Filestore API, or do not want to, an alternate solution for the \u003ccode\u003eSystem limit for internal resources has been reached\u003c/code\u003e error is to fill out a form to request a limit adjustment, or when creating new VPCs, reuse the names of old VPCs that have already been deleted.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot instance creation\n\nThis page provides troubleshooting information to help address issues you might\nencounter while attempting to create a Filestore instance.\n\n`PERMISSION DENIED` when creating a Filestore instance\n------------------------------------------------------\n\n1. Check if the Filestore API is enabled:\n\n gcloud services enable file.googleapis.com\n\n2. Each Filestore instance must have an IP address range associated\n with it that does not overlap with another range in use. For a detailed list\n of restrictions, see [Configuring a reserved IP address range](/filestore/docs/creating-instances#configure_a_reserved_ip_address_range).\n\n3. Check if you have the `roles/file.editor` role. For details see\n [Access control](/filestore/docs/access-control) or\n [IAM roles and permissions](/filestore/docs/iam).\n\n4. If you are still encountering the error, then the Filestore\n [service account](/iam/docs/service-accounts) might have had its\n `file.serviceAgent` role removed. To check if this is the case, run:\n\n gcloud projects get-iam-policy \u003cvar translate=\"no\"\u003eproject-id-or-number\u003c/var\u003e \\\n --flatten=\"bindings[].members\" \\\n --format='table(bindings.role)' \\\n --filter=\"bindings.members:service-\u003cvar translate=\"no\"\u003eproject-number\u003c/var\u003e@cloud-filer.iam.gserviceaccount.com\"\n\n where:\n - \u003cvar translate=\"no\"\u003eproject-id-or-number\u003c/var\u003e is the ID or number of your Google Cloud project.\n - \u003cvar translate=\"no\"\u003eproject-number\u003c/var\u003e is the number of your Google Cloud project.\n\n The command should return something similar to the following: \n\n ```\n ROLE\n roles/file.serviceAgent\n ```\n\n If `roles/file.serviceAgent` is not listed, you can restore it by running: \n\n gcloud projects add-iam-policy-binding \u003cvar translate=\"no\"\u003eproject-id-or-number\u003c/var\u003e \\\n --member serviceAccount:service-\u003cvar translate=\"no\"\u003eproject-number\u003c/var\u003e@cloud-filer.iam.gserviceaccount.com \\\n --role roles/file.serviceAgent\n\n`System limit for internal resources has been reached` error when creating an instance\n--------------------------------------------------------------------------------------\n\nThis error is caused by Filestore reaching an internal network\nquota. For every VPC network that you create a Filestore instance\non, Filestore must create an\n[internal network](/filestore/docs/networking#connectivity)\nthat peers with that network. These internal networks are preserved even\nwhen the Filestore instances and VPC networks associated with them\nare deleted.\n\nOnce the number of internal networks reaches 49 for a project,\nFilestore is no longer able to create new internal networks, which\nprevents you from creating Filestore instances on new VPC networks.\nAttempting to do so results in one of the following errors:\n\n`System limit for internal resources has been reached. Please request to adjust limit here: https://forms.gle/PFPJ2QD4KnCHzYEx9`\n\nYou can clear the internal networks by disabling and then re-enabling the\nFilestore API.\n| **Important:** Before you can disable the API, you must delete all Filestore related resources, such as Filestore instances and backups.\n| **Caution:** Disabling the Filestore API removes previously granted quota increase requests.\n\nUse the [`gcloud services disable`](/sdk/gcloud/reference/services/disable)\ncommand to disable the Filestore API: \n\n gcloud services disable file.googleapis.com\n\nThen, use the [`gcloud services enable`](/sdk/gcloud/reference/services/enable)\ncommand to re-enable the Filestore API: \n\n gcloud services enable file.googleapis.com\n\nIf you can't disable the API because you have Filestore instances\nthat you cannot delete or you don't want to lose quota that you've been granted\nthrough quota increase requests, then you can fill out the following form to\nhave your network limits adjusted: \n\n https://forms.gle/PFPJ2QD4KnCHzYEx9\n\nIf you need to regularly delete and create VPC networks and\nFilestore instances, there are two ways to avoid running out of\nnetwork quota:\n\n- When you create a VPC network, use the same name as a previous network that's\n been used for Filestore instance creation.\n\n- Cycle through a pool of no more than 49 VPC networks instead of deleting and\n then recreating them.\n\nWhat's next\n-----------\n\n- [Known issues](/filestore/docs/known-issues)\n- [Troubleshoot slow performance](/filestore/docs/troubleshooting)"]]
