[[["易于理解","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 and clients cannot use IP addresses within the \u003ccode\u003e172.17.0.0/16\u003c/code\u003e range due to internal component usage.\u003c/p\u003e\n"],["\u003cp\u003eWindows NFS clients may experience slow responses when creating folders or deleting files, which can be improved by creating a firewall rule to block NetBIOS and SMB traffic on ports 445 and 139.\u003c/p\u003e\n"],["\u003cp\u003eIf a region displays a default capacity quota of 0 for a particular service tier, you must request a quota increase before creating a Filestore instance of that tier.\u003c/p\u003e\n"],["\u003cp\u003eCopying data from Cloud Storage to Filestore can be slow, but performance can be improved by following specific guidelines, and the Storage Transfer Service is available for large datasets.\u003c/p\u003e\n"],["\u003cp\u003eMounting over a VPN can fail if client and Filestore instance subnet ranges overlap, or if the Cloud Router is not configured to advertise the Filestore instance's IP address, in addition, the use of an external or third-party VPN provider is necessary.\u003c/p\u003e\n"]]],[],null,["# Known issues\n\nFilestore has the following known issues.\n\nFilestore instances and clients can't have an IP address from the `172.17.0.0/16` subnet range\n----------------------------------------------------------------------------------------------\n\nFilestore instances use the `172.17.0.0/16` address range for internal\ncomponents. As a result, the following limitations apply:\\\\\n\n- Clients with an IP address from the `172.17.0.0/16` range can't connect to Filestore instances.\n\n\u003c!-- --\u003e\n\n- You can't create a Filestore instance with a reserved IP range that overlaps with the range `172.17.0.0/16`.\n\nSlow response on Windows NFS clients\n------------------------------------\n\nOn some Windows NFS clients, it can take 20+ seconds to create a folder or\ndelete files. To improve client response, use the following procedure to create\na Windows firewall rule to block network traffic to the ports used by\nNetBIOS and SMB, usually ports 445 and 139.\n\n1. Open the **Windows Firewall with Advanced Security** snap-in in the Microsoft Management Console.\n2. In the left-hand pane, click **Outbound Rules**.\n3. In the right-hand **Actions** pane, click **New Rule**.\n4. In the **New Outbound Rule Wizard** , select the **Port** radio button and then click **Next**.\n5. Select the **TCP** radio button, select the **Specific Remote ports** radio button, and then type **445, 139** in the field next to the **Specific Remote ports** radio button. Click **Next**.\n6. Select the **Block the connection** radio button and then click **Next**.\n7. Select the **Domain** , **Private** , and **Public** checkboxes, and then click **Next**.\n8. Type a name for the firewall rule, and then click **Finish**.\n\nNo quota for a particular service tier in a particular region\n-------------------------------------------------------------\n\nIf a particular region shows a default capacity quota of 0 for a particular\nservice tier, you can't create a Filestore instance of that tier\nuntil quota is increased.\n\nTo fix this issue,\n[request additional quota](/filestore/docs/requesting-quota-increases).\n\nCopy data between Cloud Storage and Filestore\n---------------------------------------------\n\nCopying data from Cloud Storage to a Filestore instance using\n`gcloud` can be slow. For detailed information on how to improve performance, see\n[Improve performance across Google Cloud resources](/filestore/docs/performance#across-resources).\n\nYou can also use [Storage Transfer Service](/storage-transfer/docs/cloud-storage-to-cloud-storage)\nto move large datasets from Cloud Storage to your Filestore\nfile shares. For more information, see\n[Transfer large datasets from Cloud Storage to Filestore](/filestore/docs/transfer-data-from-gcs).\n\nFor other options, see [Copy data to or from instances](/filestore/docs/copying-data).\n\nMount over VPN\n--------------\n\n- When the subnet ranges of the client and the Filestore instance\n overlap, attempting to mount over a VPN may cause the `mount` command to\n become unresponsive.\n\n If your client is a Compute Engine VM, follow the instructions at\n [Migrating a VM](/compute/docs/instances/migrating-interfaces-between-networks#migrating-a-vm)\n and change only the **Subnetwork** field. For this field, select a subnet that\n does not overlap with the IP range of the Filestore instance.\n- If you don't explicitly configure the Cloud Router to advertise the\n IP address of the Filestore instance, attempting to mount over a\n VPN results in an error:\n\n `mount.nfs: Connection timed out`\n\n For instructions on configuring the Cloud Router to advertise the IP\n address of a Filestore instance, see\n [Advertising custom IP ranges](/network-connectivity/docs/router/how-to/advertising-custom-ip).\n- You must use an external or third-party VPN provider. For more information,\n see [Remote mounting](/filestore/docs/remote-mounting#establish-connection).\n\nCapacity errors before reaching full provisioned capacity\n---------------------------------------------------------\n\n- When you reach close to maximum capacity usage, you may receive a\n `No space left on device` error. In this case, you can [add capacity](/filestore/docs/editing-instances#scaling_capacity)\n to the instance.\n\n- Each file stored on the file share consumes one inode. If the file system runs\n out of inodes, you won't be able to store more files on the file share even\n if you haven't reached the maximum allocated capacity. If connecting to\n numerous smaller files, you may need to increase capacity. For more information,\n see [Inode usage](/filestore/docs/scale#inode-usage).\n\nWhat's next\n-----------\n\n- [List of Filestore-specific response error codes and messages](/filestore/docs/response-errors)\n- [Operations concurrency](/filestore/docs/operations-concurrency)\n- [Troubleshoot performance-related issues](/filestore/docs/troubleshooting)"]]
