Organízate con las colecciones
Guarda y clasifica el contenido según tus preferencias.
En esta página se proporciona información para solucionar problemas que pueden surgir al intentar crear una instancia de Filestore.
PERMISSION DENIED al crear una instancia de Filestore
Comprueba si la API de Filestore está habilitada:
gcloud services enable file.googleapis.com
Cada instancia de Filestore debe tener asociado un intervalo de direcciones IP que no se solape con otro intervalo en uso. Para ver una lista detallada de las restricciones, consulta Configurar un intervalo de direcciones IP reservadas.
Si sigues teniendo el error, es posible que se haya quitado el rol file.serviceAgent de la cuenta de servicio de Filestore. Para comprobar si este es el caso, ejecuta el siguiente comando:
Error System limit for internal resources has been reached al crear una instancia
Este error se debe a que Filestore ha alcanzado una cuota de red interna. Por cada red de VPC en la que crees una instancia de Filestore, Filestore debe crear una red interna que se empareje con esa red. Estas redes internas se conservan incluso cuando se eliminan las instancias de Filestore y las redes de VPC asociadas.
Cuando el número de redes internas de un proyecto llega a 49, Filestore ya no puede crear más redes internas, lo que te impide crear instancias de Filestore en redes de VPC nuevas.
Si intenta hacerlo, se producirá uno de los siguientes errores:
System limit for internal resources has been reached. Please request to adjust limit here: https://forms.gle/PFPJ2QD4KnCHzYEx9
Para borrar las redes internas, inhabilita y vuelve a habilitar la API de Filestore.
A continuación, usa el comando gcloud services enable
para volver a habilitar la API Filestore:
gcloud services enable file.googleapis.com
Si no puedes inhabilitar la API porque tienes instancias de Filestore que no puedes eliminar o no quieres perder la cuota que se te ha concedido mediante solicitudes de aumento de cuota, puedes rellenar el siguiente formulario para que se ajusten los límites de tu red:
https://forms.gle/PFPJ2QD4KnCHzYEx9
Si necesitas eliminar y crear redes de VPC e instancias de Filestore con frecuencia, tienes dos formas de evitar que se agote la cuota de red:
Cuando cree una red de VPC, use el mismo nombre que una red anterior que se haya usado para crear instancias de Filestore.
Alterna entre un grupo de no más de 49 redes VPC en lugar de eliminarlas y volver a crearlas.
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-21 (UTC)."],[[["\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)"]]
