Managing File Systems
In the File Storage service, file systems are associated with a single compartment. When you select a compartment, the Console displays all file systems in the compartment. You can also see exports and snapshots associated with each file system. If there are no file systems in the compartment, see Creating File Systems for instructions about creating one.
The compartment has policies that indicate what actions a user can take to manage file system. UNIX permissions control what actions a user can take on the files stored in the file system. See About File Storage Security for more information.
You can perform the following file system management tasks:
- Listing File Systems
- Getting a File System's Details
- Editing a File System
- Moving a File System Between Compartments
- Moving a File System to Another Subnet
- Encrypting a File System
- Setting a File System's Reported Size
- Deleting a File System
You can perform most administrative tasks for your file systems 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.
To access a file system, it must have at least one export in one mount target. Next, mount the file system from an instance, and then you can create directories and read and write files. For more information about creating an export for a file system, see Working with NFS Exports and Export Options. For more information about accessing your file system, see Mounting File Systems.
Limitations and Considerations
- Each tenancy in a region can have one
ChangeFilesystemCompartmentoperation in progress at a time. See 409 error occurs when creating or moving a file system or mount target for more information.
Details About Your File System
The file system details page provides the following information about your file system:
- FILE SYSTEM OCID
- Every Oracle Cloud Infrastructure resource has an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). You need your file system's OCID to use the Command Line Interface (CLI) or the API. You also need the OCID when contacting support. See Resource Identifiers.
- Availability Domain
- When you create a file system, 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 file system's availability domain to use the Command Line Interface (CLI) or the API. For more information, see Regions and Availability Domains.
- The date and time that the file system was created.
- When you create a file system, 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 only accessible to those groups that have been given permission by an administrator in your organization. You need your file system's compartment to use the Command Line Interface (CLI) or the API. For more information, see Managing Compartments.
- Metered size of the file system that gets updated hourly. If the file system is a clone, this value represents only the differentiated data unique to the clone. For more information, see File System Usage and Metering.
- Indicates whether the file system is a clone currently copying metadata from its source. See Cloning File Systems.
- SOURCE SNAPSHOT
- If the file system is a clone, a link is provided to the clone's source snapshot. If the source snapshot is deleted, the link is disabled. See Cloning File Systems.
- PARENT FILE SYSTEM
- If the file system is a clone, a link is provided to the clone's parent file system. See Cloning File Systems.
- Indicates whether the file system is the root of a clone tree. See Cloning File Systems.
- Indicates whether the file system has been cloned. See Cloning File Systems.
- Indicates whether this file system can be used as a target file system for replication. The system sets this value to
trueif the file system is unexported, has no user snapshots, and hasn't yet been specified as a target file system in any replication resource. After the file system has been specified as a target in a replication, this value is
false, since a target file system can only be used for one replication. If the file system was specified as a target in a replication but never exported, and the replication is subsequently deleted, this value can revert to
true. This value is always
falsefor a source file system. See File System Replication for more information.
- REPLICATION TARGET
- A link to any replication target associated with this file system. This value is
nullfor a source file system since a replication target is always associated with the target file system. See File System Replication for more information.
- Resources such as exports and snapshots that are associated with the file system are listed here. Click the resource type link to see a list of each individual resource. Each export in the list shows the file system's export path and mount target. You need the export path to mount a file system.
Required IAM Service Policy
To use Oracle Cloud Infrastructure, you must be granted security access in a policy by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment to work in.
For administrators: The policy in Let users create, manage, and delete file systems allows users to manage file systems.