Before You Start: NFS Setup Requirements
Make sure the following conditions are met before using the MapR NFS gateway:
- The stock Linux NFS service must not be running. Linux NFS and MapR NFS cannot run concurrently.
- The lock manager (nlockmgr) must be disabled.
- On Red Hat and CentOS v6.0 and higher, the
rpcbind
service must be running. You can use the commandps ax | grep rpcbind
to check. - On Red Hat and CentOS v5.x and lower, and on Ubuntu and SUSE,
the
portmapper
service must be running. You can use the commandps ax | grep portmap
to check. - The
mapr-nfs
package must be present and installed. You can list the contents in the/opt/mapr/roles
directory to check fornfs
in the list. - Make sure you have applied a Community Edition (M3) license or an Enterprise Edition (M5) license (paid or trial) to the cluster. See Adding a License.
- Make sure the MapR NFS service is started. See Managing Roles and Services.
- Verify that the primary group of the user listed for
mapr.daemon.user
in the/opt/mapr/conf/daemon.conf
file ismapr.daemon.group
. Restart Warden after any changes todaemon.conf
.
For information about mounting the cluster via NFS, see Accessing Data with NFS.
For information on upgrading your cluster, see Upgrade Guide.
To preserve compatibility with 32-bit applications and system
calls, MapR-NFS uses 32-bit inode numbers by default. On 64-bit
clients, this default forces the client's 64-bit inode numbers to
be hashed down to 32 bits. Hashing 64-bit inodes down to 32 bits
can potentially cause inum conflicts. To change the default
behavior to 64-bit inode numbers, set the value of the
Use32BitFileId
property to 0 in the
nfsserver.conf
file, then restart the NFS server.