NFS Helper

Updated -

The NFS Helper app simplifies the configuration of a new NFS server or client by walking through the setup steps and exposing the various available export and mount options. On completing the steps provided by the application and clicking "Generate," a script will be provided based on the information collected. Running this script will prepare the target system for its defined role as an NFS server or client.

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Get notified when this content is updated

Follow

1 Comments

Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

have no chance to try it, but looks great!

the 'ADD' button in the 'NFS Client Hosts' screen doesn't work if you use an unqualified hostname. Works OK with IP address or FQDN.

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.

how to Place the appropriate restrictions on all NFS shares.

Couple of problems. - Can only specify FQDN, individual IPs, or * for NFS Client Hostname. I am not entering 254 comma separated addresses when the system syntax supports /24 prefix notation. - Usage command is invalid syntax for default root environment and default user environment:

[root@builder2 ~]# chmod +x nfsserver.sh $ ./nfsserver.sh
chmod: cannot access ‘$’: No such file or directory
  • Generated script is not compliant with default shell environment in RHEL7.
[root@builder2 ~]# ./nfsserver.sh
-bash: ./nfsserver.sh: /bin/bash^M: bad interpreter: No such file or directory

On that last one, the ^M tells me what the problem is obviously Windows control character Carriage Return or \r. Why it is in a linux script is beyond me. I downloaded the script to a Windows workstation and moved it to RHEL7 via WinSCP. I downloaded the script, compressed it with a zip file, and moved it to RHEL7 via WinSCP. I copied the text in the web browser window, pasted into a PuTTy ssh terminal on RHEL7 into a document opened with VIM. I even downloaded it directly to RHEL7 system via Firefox on Gnome3. In every single case the carriage return characters appear. It is easy to fix. But, seriously? I have to break out dos2unix or a perl script to fix this myself?

Hi Jeff,

Based on your feedback, we have updated the NFS Helper application.

  • Modified the usage command.
$ chmod +x nfsserver.sh
$ ./nfsserver.sh
  • The download script does not contain ^M character ( carriage return \r). Now the user can download the script and run as mentioned in the usage section.

Something is fubar.