NFS

DataCore vFilO provides data access over NFS and SMB to clients including Linux, Windows, and MacOS.

Supported NFS Protocols

NFS Version	Status
Version 3	Red Hat Enterprise Linux 7.7, 7.8, & 7.9 clients: Supported Red Hat Enterprise Linux 8.2, & 8.3 clients: Support added in DataCore vFilO release version 4.6.3. Ubuntu Version 20.04 or earlier: Supported
Version 4.1	Version 4.1 – Not supported. Most Linux clients default to using version 4.1 when using the mount command without specifying the protocol version. This can be changed by editing the defaults configuration file (OS specific)
Version 4.2	Red Hat Enterprise Linux 7.7, 7.8, & 7.9 clients: Already supported with previous DataCore vFilO releases (version 4.6). Red Hat Enterprise Linux 8.2, & 8.3 clients: Support added in DataCore vFilO release version 4.6.3. If a client tries to access and it is not on the qualified list, it will transparently be re-directed to NFS v3 protocol version and the mount will succeed. NFS 4.2 clients must have network access to all storage volumes where data may be stored. For RHEL / CentOS 7.x clients, make sure the client flexfiles timeout is adjusted due to an incorrect default value. Add the following single line to /etc/modprobe.d/hs_flex.conf and reboot the client: options nfs_layout_flexfiles dataserver_retrans=0 dataserver_timeo=600

NFS Version

Status

Version 3

Red Hat Enterprise Linux 7.7, 7.8, & 7.9 clients: Supported
Red Hat Enterprise Linux 8.2, & 8.3 clients: Support added in DataCore vFilO release version 4.6.3.
Ubuntu Version 20.04 or earlier: Supported

Version 4.1

Version 4.1 – Not supported.

Most Linux clients default to using version 4.1 when using the mount command without specifying the protocol version. This can be changed by editing the defaults configuration file (OS specific)

Version 4.2

Red Hat Enterprise Linux 7.7, 7.8, & 7.9 clients: Already supported with previous DataCore vFilO releases (version 4.6).
Red Hat Enterprise Linux 8.2, & 8.3 clients: Support added in DataCore vFilO release version 4.6.3.

If a client tries to access and it is not on the qualified list, it will transparently be re-directed to NFS v3 protocol version and the mount will succeed.

NFS 4.2 clients must have network access to all storage volumes where data may be stored.

For RHEL / CentOS 7.x clients, make sure the client flexfiles timeout is adjusted due to an incorrect default value. Add the following single line to /etc/modprobe.d/hs_flex.conf and reboot the client:

options nfs_layout_flexfiles dataserver_retrans=0 dataserver_timeo=600

The NFSv4 protocol requires that each client has a unique ID. By default, the Linux NFS client uses an ID string that contains the local node name, therefore if all node names are unique no further action is required. Failure to use unique IDs on nodes will result in unreliable NFS v4 operations.

If node names are not unique the following steps can be used to assign a unique NFSv4 id:

Execute # echo "options nfs nfs4_unique_id=`uuidgen`" >> /etc/modprobe.d/local.conf.
Reboot the client.
Execute
# umount -a -t nfs; modprobe -r nfs; mount -a -t nfs”
(assumes all current NFS mounts are in /etc/fstab)

For more details please refer to the NFS client documentation.