Oracle Cloud Infrastructure Documentation

Managing Mount Targets

Mount targets are attached to VCN subnets and represent the network access point to one or more file systems by Compute instances. File systems must be associated with a mount target for any instance to mount and use the file systems. You create your first mount target when you create your first file system. Mount targets can be associated with one or many file systems, and file systems with one or many mount targets. In the Console, mount targets appear as a resource of each file system they are associated with, and are accessed through the file system details page. Mount targets that aren't associated with any file system are accessed in "Manage Mount Targets". This tool appears at the top of the file system list only if you have unassociated mount targets.

When you associate a file system with a mount target, you define an export path for the file system. The export path uniquely identifies the file system within that mount target. The file system export path, along with the mount target IP address, is used to mount the file system to an instance.

Note

To simplify file system management, exports and export sets are managed by the File Storage service when you use the Console. More advanced configuration options for exports and export sets are available in the Command Line Interface (CLI) and API.

Actions you can take to manage a mount target include:

  • Viewing mount target details
  • Obtaining mount command samples
  • Associating a new or previously created file system with a mount target
  • Deleting a mount target

You can perform most administrative tasks for your mount targets using the Console, Command Line Interface (CLI), or API. You can use the Console to list mount targets exporting a specific file system. Use the API or CLI if you want to list all mount targets in a compartment.

Limitations and Considerations

  • Each availability domain is limited to two mount targets by default. However, you can associate up to 100 file systems with each mount target.
  • See Service Limits for a list of applicable limits and instructions for requesting a limit increase.

  • Mount targets can't be created independently of file systems. They must be created along with the file system or added from the details page of a file system. The mount target is created in the same availability domain as the file system.
  • Each mount target requires three internal IP addresses in the subnet to function. Two of the IP addresses are used during mount target creation. The third IP address must remain available for the mount target to use for high availability failover.
  • The File Storage service doesn't "reserve" the third IP address required for high availability failover. Use care when designing your subnets and file systems to ensure that sufficient IP addresses remain available for your mount targets.
  • If one file system associated to a mount target has '/' specified as an export path, you can't associate another file system with that mount target. No two file systems associated with the same mount target can have an export path that contains a complete path of the other. For more information on this limitation, see Paths in File Systems.

Tagging Resources

You can apply tags to your resources to help you organize them according to your business needs. You can apply tags at the time you create a resource, or you can update the resource later with the desired tags. For general information about applying tags, see Resource Tags.

Details About Your Mount Target

The mount target details page provides the following information about your mount target:

Mount Target OCID
Every Oracle Cloud Infrastructure resource has an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). You need your mount target's OCID to use the Command Line Interface (CLI) or the API. You'll also need it when contacting support.
Availability Domain
When you create a mount target, you specify the availability domain that it resides in. An availability domain is one or more data centers located within a region. You need your mount target's availability domain to use the Command Line Interface (CLI) or the API. For more information, see Regions and Availability Domains.
Created
The date and time that the mount target was created.
Compartment
When you create a mount target, you specify the compartment that it resides in. A compartment is a collection of related resources (such as cloud networks, compute instances, or file systems) that are accessible only to those groups that have been given permission by an administrator in your organization. You need your mount target's compartment to use the Command Line Interface (CLI) or the API. For more information, see Managing Compartments.
Private IP Address
The private IP address that was assigned to the mount target when it was created. You need your mount target's private IP address to mount associated file systems.
Maximum Free Space
The maximum free space value represents the reported available space for each file system exported through the mount target. The default value is 8 exabytes of available capacity. This value can be changed if necessary to application installation. See To set the maximum reported free space for more information.
Resources
File systems that are associated with the mount target are listed here. The export path of each file system is also listed. You need the export path to mount a file system.

Warning

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in.

For administrators: The policy in Let users create, manage, and delete file systems allows users to manage mount targets. Since mount targets are network endpoints, users must also have "use" permissions for VNICs, private IPs, private DNS zones and subnets to create or delete a mount target. See the Policy Reference for more information.

If you're new to policies, see Getting Started with Policies and Common Policies.

Using the Console

To view details of a mount target associated with a file system
To view details of unassociated mount targets
To add more file systems to a mount target
To set the maximum reported free space
To manage tags for a mount target
To delete a mount target associated with a file system
To delete unassociated mount targets

Using the Command Line

For information about using the CLI, see Command Line Interface (CLI).

To create a mount target
To update a mount target
To delete a mount target
To list mount targets
To get a specific mount target
To create an export
To list exports
To get a specific export
To delete an export
To list export sets
To get a specific export set
To update an export set
To set the export set reported free space

Using the API