Last updated on SEPTEMBER 14, 2017
Applies to:Oracle VM - Version 3.3.1 and later
Linux OS - Version Oracle Linux 6.0 and later
A Network File System (NFS) server can share directory hierarchies in its local file systems with remote client systems over an IP-based network. After an NFS server exports a directory, NFS clients mount this directory if they have been granted permission to do so. The directory appears to the client systems as if it were a local directory. NFS centralizes storage provisioning and can improves data consistency and reliability.
Oracle Linux supports three versions of the NFS protocol:
NFS version 2 (NFSv2), specified in RFC 1094.
NFS version 3 (NFSv3), specified in RFC 1813.
NFS version 4 (NFSv4), specified in RFC 3530.
NFSv2 and NFSv3 rely on Remote Procedure Call (RPC) services, which are controlled by the rpcbind service. rpcbind responds to requests for an RPC service and sets up connections for the requested service. In addition, separate lockd and rpc.statd services are used to handle locking and mounting protocols. Configuring a firewall to cope with the various ranges of ports that are used by all these services is complex and error prone.
NFSv4 does not use rpcbind as the NFS server itself listens on TCP port 2049 for service requests. The mounting and locking protocols are also integrated into the NFSv4 protocol, so the lockd and rpc.statd services are also not required. These refinements mean that firewall configuration for NFSv4 is no more difficult than for a service such as HTTP.
By default, NFSv4 is used on Oracle Linux 6.x and Oracle VM Server 3.3.x.
This document describes how to set NFSv3 instead of NFSv4 as default on Oracle Linux 6.x and Oracle VM Server 3.3.x.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms