NFS Helper

When I use the tool to do a mount of NFSv4 on RHEL5 client it says uise of NFSv4 on RHEL5 is not recommended. Is that still true for later versions of RHEL5?

I've been RHEL5.9 client mounts from an NFSv4 appliance (server) for about a month with no obvious ill effects. In fact the only reason I came here was to see the recommendations for mount options on RHEL6 as we had a client not automatically mount NFSv4 from the appliance after a reboot (which I suspect is because I need to add _netdev to the mount options in fstab). My other NFS(v3) mounts from other clients are mounting fine.

P.S. Thanks Jeff Thorsen for your note about FQDN or IP.

Hi Jeff,

The issue that cannot download script is fixed now, I'm sorry for the inconvenience, could you please give it another try?

I have confirmed this is the stock file that ships/installs with the OS. Identical file exists on other systems that do not have nfs services configured or running. Contents of said file:

#
# Note: For new values to take effect the nfs-config service
# has to be restarted with the following command:
#    systemctl restart nfs-config
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
#LOCKD_TCPPORT=32803
# UDP port rpc.lockd should listen on.
#LOCKD_UDPPORT=32769
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
RPCNFSDARGS=""
# Number of nfs server processes to be started.
# The default is 8. 
#RPCNFSDCOUNT=16
#
# Set V4 grace period in seconds
#NFSD_V4_GRACE=90
#
# Set V4 lease period in seconds
#NFSD_V4_LEASE=90
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
#MOUNTD_PORT=892
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
STATDARG=""
# Port rpc.statd should listen on.
#STATD_PORT=662
# Outgoing port statd should used. The default is port
# is random
#STATD_OUTGOING_PORT=2020
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to sm-notify. See sm-notify(8)
SMNOTIFYARGS=""
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
RPCIDMAPDARGS=""
#
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
# Note: The rpc-gssd service will not start unless the 
#       file /etc/krb5.keytab exists. If an alternate
#       keytab is needed, that separate keytab file
#       location may be defined in the rpc-gssd.service's
#       systemd unit file under the ConditionPathExists
#       parameter
RPCGSSDARGS=""
#
# Enable usage of gssproxy. See gssproxy-mech(8).
GSS_USE_PROXY="yes"
#
# Optional arguments passed to blkmapd. See blkmapd(8)
BLKMAPDARGS=""

Thank you Jeff. We will look at this problem as soon as possible.

The tool presumably generated the nfs_client.sh script information based on what you input. I'm not sure if it showed it to you and asked you to cut and paste to a file of that name or if it gave you one to download.

A "here-document" is setup that allows one to execute multiple commands as a group almost as if they are one. Typically it begins with a redirection (<<) from the final line which is often the literal text "EOF" (e.g. <<EOF). That tells it to do all the commands that follow until it sees the text specified (e.g. EOF). The error you got said there is no text "EOF" before it gets to the actual end of file (which is also called EOF just to confuse everyone).

If you cut and pasted the script you may have left out the literal "EOF" text (and maybe more). If it gave you a script to download it may have had a bug in that it left out the literal "EOF".

Note that although "EOF" is usual for here-documents it is possible to use other text instead.