Known issues

Filestore has the following known issues.

Clients can't have an IP address from the 172.17.0.0/16 range

Clients with an IP address from the 172.17.0.0/16 range can't connect to Filestore instances.

Slow response on Windows NFS clients

On some Windows NFS clients, it can take 20+ seconds to create a folder or delete files. To improve client response, use the following procedure to create a Windows firewall rule to block network traffic to the ports used by NetBIOS and SMB, usually ports 445 and 139.

  1. Open the Windows Firewall with Advanced Security snap-in in the Microsoft Management Console.
  2. In the left-hand pane, click Outbound Rules.
  3. In the right-hand Actions pane, click New Rule.
  4. In the New Outbound Rule Wizard, select the Port radio button and then click Next.
  5. 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.
  6. Select the Block the connection radio button and then click Next.
  7. Select the Domain, Private, and Public checkboxes, and then click Next.
  8. Type a name for the firewall rule, and then click Finish.

No quota for a particular service tier in a particular region

If a particular region shows a default capacity quota of 0 for a particular service tier, you can't create a Filestore instance of that tier until quota is increased.

To fix this issue, request additional quota.

Filestore instances on the shared VPC network cannot be created from service projects

If you attempt to create a Filestore instance from a service project that is attached to a shared VPC host project, the shared VPC network is not listed under Authorized network. Similarly, attempting to create the instance using gcloud or the REST API results in the following error:

ERROR: (gcloud.filestore.instances.create) INVALID_ARGUMENT: network '[SHARED_VPC_NETWORK]' does not exist.

Workaround 1: Create the Filestore instance from the host project

You can create Filestore instances from the host project with the shared VPC as the authorized network. Once created, clients in any service project can mount the instance as usual.

The caveats to this workaround include:

  • The host project must be involved in the creation of Filestore instances.
  • Costs for Filestore instances are charged to the host project instead of the service projects that use them.

Workaround 2: Mount over a VPN

For detailed instructions, see Mounting file shares on remote clients.

Copying data between Cloud Storage and Filestore

Copying data from Cloud Storage to a Filestore instance using gsutil is currently known to be slow. There is no known mitigation.

Mounting over VPN

  • When the subnet ranges of the client and the Filestore instance overlap, attempting to mount over a VPN may cause the mount command to become unresponsive.

    If your client is a Compute Engine VM, follow the instructions at Migrating a VM and make changes to only the Subnetwork field and select a subnet that does not overlap with that of the Filestore instance.

  • If you don't explicitly configure the Cloud Router to advertise the IP address of the Filestore instance, attempting to mount over a VPN results in an error:

    mount.nfs: Connection timed out

    For instructions on configuring the Cloud Router to advertise the IP address of a Filestore instance, see Advertising custom IP ranges.