Oracle Cloud Infrastructure Documentation

Mounting File Systems From Unix-Style Instances

Users of Ubuntu and Linux operating systems can use the command line to connect to a file system and write files. Mount targets serve as network access points for file systems. After your mount target is assigned an IP address, you can use it together with the export path to mount the file system. On the instance from which you want to mount the file system, you need to install an NFS client and create a mount point. When you mount the file system, the mount point effectively represents the root directory of the File Storage file system, allowing you to write files to the file system from the instance.

Prerequisites

  • The file system must have at least one export in at least one mount target. When you create a new file system, an export for the file system is created at the same time. See Creating File Systems for more information.
  • Correctly configured security list rules in the VCN subnet where the file system's associated mount target resides. See Security Lists for information about how security lists work in Oracle Cloud Infrastructure. Use the instructions in Configuring VCN Security List Rules for File Storage to set up security lists for your file systems.

Mounting File Systems

You can use the following instructions to construct your mount commands, or use the Console to get mount command samples that include all the information for a specific mount target and file system. For more information, see To get mount command samples.

Warning

When mounting file systems, the following mount option combination is not supported by the File Storage service:

  • soft when the file system is mounted with the read/write mount option (-o rw). This combination can cause corruption of your data.

The following mount options or mount option combinations are not recommended for use with the File Storage service:

  • soft when the file system is mounted with the read-only mount option (-o ro) and the timeo has been specified as less than 300 seconds. This combination can cause a profusion of I/O error responses.
  • nolock, rsize, or wsize. These options cause issues with performance and file locking.
To mount a file system from Ubuntu or Debian
To mount a file system from Linux, Red Hat, or CentOS
To mount a file system from a Database VM instance
To auto-mount a shared file system