Configuration of the NFS service on ''hpa'': Difference between revisions

From Lsdf
Jump to navigationJump to search
mNo edit summary
mNo edit summary
Line 13: Line 13:
* nfs-utils was updated with yum
* nfs-utils was updated with yum


* nfs was startetd with <b>systemctl start nfs.service</b>
* nfs was started with <b>systemctl start nfs.service</b>




Line 22: Line 22:
* nfs v4 : mount -o nfsvers=4 <server>:/ /mnt
* nfs v4 : mount -o nfsvers=4 <server>:/ /mnt


Also rpcbind has to be run on the v3 server
Also rpcbind has to be run on an v3 server


service rpcbind start
systemctl start rpcbind

Revision as of 11:45, 24 June 2016

The directory on the HPSS servers for the configuration files is: TBD
With changing to this directory the automount will be active.
The mount will be unmounted after 3 minutes without access.

Configuration on the HPA server (172.18.95.59)

  • the directory for the config files was created: /export/hpa
  • The file /etc/exports was modified:
      /export/hpa 172.18.95.0/22(rw,no_subtree_check,no_acl,no_root_squash)
  • nfs-utils was updated with yum
  • nfs was started with systemctl start nfs.service


NFS v3 support

Because RH systems run NFS Version 4 by default the mount syntax on the client is different as compared to mounting the same directory with the nfs 4 protocol. nfs v4 uses the 'root' directory concept and therefore mount commands must mount the exported 'root'. If the server has the /etc/exports file above then

  • nfs v3 : mount -o nfsvers=3 <server>:/export/hpa /mnt
  • nfs v4 : mount -o nfsvers=4 <server>:/ /mnt

Also rpcbind has to be run on an v3 server

 systemctl start rpcbind