Oracle Cloud Infrastructure Documentation

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 Security for more information.

Actions you can take to manage a file system include:

  • Viewing file system details
  • Editing file system settings
  • Viewing associated file system resources
  • Creating an export for the file system
  • 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 To create an export for a file system in this topic. For more information about accessing your file system, see Mounting File Systems.

Required IAM Service 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 file systems.

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

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.

Moving File Systems to a Different Compartment

You can move file systems from one compartment to another. When you move a file system to a new compartment, its associated snapshots move with it. After you move the file system to the new compartment, inherent policies apply immediately and affect access to the file system and snapshots through the Console. Moving these resources doesn't affect access to file systems and snapshots from mounted instances. For more information, see Managing Compartments.

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.
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.
Created
The date and time that the file system was created.
Compartment
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.
Utilization
Metered size of the file system that gets updated hourly.
Important

There can be a delay of up to 1 hour when reporting file system usage.
You can use df or du commands from your mounted instance command line application to view usage information about your file system.
  • df provides the amount of storage metered for your file system. Results are returned quickly, but can be up to 1 hour out of date.
  • du provides the storage used by a directory hierarchy. The du command walks the directory tree, and if your hierarchy is large, it can take a long time to run and return results.
The results provided by df and du can differ for several reasons:
  • df and du report snapshot utilization differently. Snapshots are copy-on-write, so each snapshot shares the blocks used by the unchanged data. The df command retrieves information provided by the File Storage service using the NFS FSSTAT call, which accounts correctly for the shared utilization. The du command can't detect this sharing, and reports the shared utilization once for each snapshot.
  • df counts each file only once. du may count files with hard links more than once.
  • File Storage needs 512 bytes for each directory entry and 8192 bytes for each symlink for metadata cost. df reports this cost usage, even on empty files. du reports empty files as using zero bytes.
Resources
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.

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.

Using the Console

To view file system details
To change the file system name
To create an export for a file system
To set the file system reported size
To manage tags for a file system
To move a file system to a different compartment
To delete a file system

Using the Command Line Interface (CLI)

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

To list file systems
To get a specific file system
To update a file system
To create an export for a file system
To set the file system reported free space
To move a file system to a different compartment
To delete a file system

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following operations to manage file systems: