Filesystem

​

Summary

• Create a project-scoped, region-bound shared filesystem
• Attach the filesystem to a single network so multiple instances/clusters in that network can share it
• Define snapshot policies to automate point-in-time filesystem snapshots
• Retrieve the NFS mount command and use it to mount the filesystem from your compute resources

​

Availability

​

Requirements

• Permissions to create and manage storage resources in the console
• A target region selected for the storage resource (Filesystem is region-bound)
• A network to attach the storage to (Filesystem attaches to a single network)
• At least one instance or cluster in the same network where you will mount the filesystem

​

Filesystem lifecycle

​

Snapshot policies

​

Schedule options

​

API behavior

{
  "snapshotPolicies": [
    {
      "name": "daily",
      "schedule": {
        "interval": "daily",
        "timeOfDay": "04:00Z"
      },
      "retention": {
        "keep": 7
      }
    },
    {
      "name": "weekly",
      "schedule": {
        "interval": "weekly",
        "dayOfWeek": "monday",
        "timeOfDay": "02:30Z"
      },
      "retention": {
        "keep": 4
      }
    }
  ]
}

​

Step-by-step

1. Choose the project and region
   • In the Console, select the project you want to use under All Projects
   • Select the region where you want the filesystem to live
2. Create (or select) the network you will attach storage to
   • Create a new network, or select an existing one in the same region
   • Confirm the network is in the same region as the storage you plan to create
   • Important: Filesystem supports a single network attachment. Plan accordingly if you have multiple networks
3. Create the Filesystem
   • Go to Storage → Filesystem in the console
   • Provide the required values (for example: name and capacity)
   • Create the filesystem
   • You should see the filesystem appear in the resource list, and its status move to a “ready/available” state
4. Configure snapshot policies (optional)
   • Use the Snapshot policies section when creating or editing the filesystem
   • Review Default Snapshot Protection, which is enabled by default
   • Add user-managed policies if you need additional cadences, UTC schedules, or retention rules
   • Save the filesystem and verify each user-managed policy reaches a ready/provisioned state
5. Get the NFS mount command
   • In the filesystem details, locate the action or section to Mount your filesystem
   • Copy the NFS mount command
   • You should see a mount command that you can run from a Linux host in the attached network
6. Mount from your compute (instance or cluster)
   • From a target instance (or nodes in your cluster) that are connected to the same network:
     • Run the mount command you copied
   • Confirm the mount worked by verifying the mount point is accessible and read/write as expected

​

View filesystem details

• Overview — filesystem status, capacity, attached VPC, and mount command
• Instances — all instances in the attached VPC that can access this filesystem, with search filtering
• Snapshot policies — schedules, retention, and provisioning state for each policy

​

Quotas

​

Common issues / troubleshooting

1. Symptom: You can’t attach the filesystem to the selected network Likely cause: The filesystem is already attached to a different network (single network attachment), or the network is in a different region. Fix: Verify the filesystem’s current attachment and region. If it’s attached already, detach it first and re-attach to the intended network. Ensure network and filesystem are in the same region.
2. Symptom: The mount command fails from your instance/cluster Likely cause: The instance/cluster is not in the attached network, or network access rules prevent NFS connectivity. Fix: Confirm the compute resource is connected to the same network the filesystem is attached to. Then verify network/security rules permit NFS traffic (exact ports/rules depend on your setup).
3. Symptom: No mount command is shown in the filesystem details Likely cause: No VPC has been selected for the filesystem. Fix: Edit the filesystem and select a VPC. The mount command will appear once a VPC is attached.
4. Symptom: A snapshot policy is rejected or does not provision Likely cause: The policy name, schedule, or retention does not match the validation rules. Common issues include using a non-UTC time, setting timeOfDay on an hourly policy, omitting dayOfWeek on a weekly policy, or using a monthly dayOfMonth after 28. Fix: Update the policy so the schedule fields match its cadence and keep is at least 1.
5. Symptom: Existing snapshot policies changed after an API update Likely cause: API updates replace the full snapshotPolicies list when a non-empty list is supplied, or clear all user-managed policies when [] is supplied. Fix: Include every policy you want to keep in the update request. Omit snapshotPolicies if you only want to update other filesystem fields.
6. Symptom: A policy named system-default is rejected Likely cause: Default Snapshot Protection is enabled or is still cleaning up, so system-default is reserved for the platform-managed policy. Fix: Use a different policy name, or wait until Default Snapshot Protection has been disabled and cleanup has completed before claiming that name.

​

Related resources