Oracle Cloud Infrastructure Documentation

Mounting File Systems From Windows Instances

Users of Windows Server 2008 R2, 2012 R2, or 2016 can mount a file system on any available drive letter using the mount target IP address and the file system export path.

On the instance from which you want to mount the file system, you need to install the Windows NFS client.

Warning

Installing the Windows NFS client may require a restart of your system.

Access to NFS file systems requires UNIX-style user and group identities, which are not the same as Windows user and group identities. To enable users to access NFS shared resources, Windows client for NFS accesses file systems anonymously, using 'AnonymousGid' and 'AnonymousUid'. On brand new file systems, write permissions are only granted to the root user. The 'AnonymousGid' and 'AnonymousUid' identity values must be changed to allow write access.

Warning

Updating the 'AnonymousGid' and 'AnonymousUid' values require registry changes to your system.

After you have installed the NFS client and correctly mapped user identities, you can mount the file system to any available drive letter using the command line or Map network drive. You can access your file system through the chosen drive letter to write files.

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.
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.

Using Windows Command Prompt

To mount a file system from Windows Server 2008 R2 Command Prompt
To mount a file system from Windows Server 2012 R2 or 2016 Command Prompt

Using Windows File Explorer

To mount a file system from Windows Server 2008 R2 File Explorer
To mount a file system from Windows Server 2012 R2 or 2016 File Explorer