[[["易于理解","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\u003eFilestore instances do not respond to \u003ccode\u003eping\u003c/code\u003e or \u003ccode\u003etraceroute\u003c/code\u003e requests due to not allowing ICMP, but connectivity can be tested using \u003ccode\u003eshowmount\u003c/code\u003e or \u003ccode\u003erpcinfo\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eScheduled maintenance can cause temporary unresponsiveness in Filestore instances, and specific maintenance windows are not customizable or visible to customers.\u003c/p\u003e\n"],["\u003cp\u003eIf a Filestore instance was deleted while still mounted, it can cause file operations to become unresponsive, and this can be checked by verifying if the instance still exists via \u003ccode\u003egcloud filestore instances list\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003eREPAIRING\u003c/code\u003e status indicates the Filestore instance is automatically fixing itself and is unavailable, requiring no user intervention.\u003c/p\u003e\n"],["\u003cp\u003eAn \u003ccode\u003eUNAVAILABLE\u003c/code\u003e status in a Filestore instance can be triggered by changes to the Cloud KMS key state, such as disabling or destroying a key version.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot Filestore instance response errors\n\nThe following sections describe scenarios where an instance might be unresponsive\nand provides steps to help address the issue.\n\nFilestore instance not responding to `ping` or `traceroute` requests\n--------------------------------------------------------------------\n\nFilestore instances do not respond to `ping` or `traceroute`\nrequests because Filestore doesn't allow ICMP.\n\nTo test for connectivity to a Filestore instance, you can run\n`showmount` from the client: \n\n sudo showmount -e \u003cvar translate=\"no\"\u003efilestore-ip\u003c/var\u003e\n\nThe Filestore instance responds with its exported file system, for\nexample: \n\n Export list for 10.139.19.98:\n /vol1 192.168.0.0/16,172.16.0.0/12,10.0.0.0/8\n\nYou can also check whether the client can reach\nFilestore's RPC information by running: \n\n sudo rpcinfo -p \u003cfilestore-ip\u003e\n\nThe response looks like: \n\n program vers proto port service\n 100000 4 tcp 111 portmapper\n 100000 3 tcp 111 portmapper\n 100000 2 tcp 111 portmapper\n 100000 4 udp 111 portmapper\n 100000 3 udp 111 portmapper\n 100000 2 udp 111 portmapper\n 100024 1 udp 2046 status\n 100024 1 tcp 2046 status\n 100003 3 tcp 2049 nfs\n 100227 3 tcp 2049\n 100021 1 udp 4045 nlockmgr\n 100021 3 udp 4045 nlockmgr\n 100021 4 udp 4045 nlockmgr\n 100021 1 tcp 4045 nlockmgr\n 100021 3 tcp 4045 nlockmgr\n 100021 4 tcp 4045 nlockmgr\n 100005 3 udp 2050 mountd\n 100005 3 tcp 2050 mountd\n\nScheduled maintenance\n---------------------\n\nOnce in a while, Filestore becomes unresponsive for a few minutes\nand then becomes responsive again because of a scheduled maintenance event. For\nFilestore's SLA, see the [SLA](/filestore/sla) page.\n\nFilestore does not support customer-defined maintenance windows.\nThe schedule for maintenance windows for Filestore is also\nunavailable to customers.\n\nInstance was deleted while still mounted to the client\n------------------------------------------------------\n\nIf a file operation or unix command like `df`, `ls`, or any read/write operation\nstops responding, then the Filestore instance was likely deleted\nwhile still mounted to the client.\n\nCheck to see if the instance still exists: \n\n gcloud filestore instances list\n\nIf the instance is no longer listed, you can recover control by creating a new\ninstance with the same IP address and file share name as the instance that was\ndeleted. Once the instance is created, the unresponsive operation exits with an\nerror. If you don't need the Filestore instance, you can unmount\nthe file share and delete it.\n\nTo prevent something like this from happening in the future, make sure you\nunmount the Filestore instance first before deleting it.\n\nInstance shows status `REPAIRING`\n---------------------------------\n\nThe Filestore instance is in an unhealthy state from internal\ncauses beyond the user's control and is automatically repairing itself. The\ninstance is unavailable during this time and you don't need to take any further\nactions.\n\nInstance shows status `UNAVAILABLE`\n-----------------------------------\n\nIf a change in Cloud KMS key state is detected, the instance\nautomatically stops serving data. Some examples include the following:\n\n- [Disabling](/kms/docs/enable-disable#disable) a key or key version.\n- [Destroying](/kms/docs/destroy-restore#destroy) a key or key version.\n- Modifying a key's permissions.\n\nFor more information, see [Encrypt data with CMEKs](/filestore/docs/cmek#disable_or_destroy_a_key_thats_used_by_an_instance)."]]
