Configuration of the NFS service on ''hpa'': Difference between revisions
From Lsdf
Jump to navigationJump to search
(Created page with " The directory on the HPSS servers for the configuration files is: <b>TBD</b> With changing to this directory the automount will be active. The mount will be unmounted after...") |
mNo edit summary |
||
| Line 14: | Line 14: | ||
* nfs was startetd with <b>systemctl start nfs.service</b> |
* nfs was startetd with <b>systemctl start nfs.service</b> |
||
==NFS v3 support== |
|||
Because RH systems run NFS Version 4 by default the mount on the client must be different as compared to NFS 3 mount. NFS v4 uses the 'root' directory concept and therefore mount commands must mount the exported 'root'. With the /etc/exports file above |
|||
* 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 the v3 server |
|||
service rpcbind start |
|||
Revision as of 11:42, 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 startetd with systemctl start nfs.service
NFS v3 support
Because RH systems run NFS Version 4 by default the mount on the client must be different as compared to NFS 3 mount. NFS v4 uses the 'root' directory concept and therefore mount commands must mount the exported 'root'. With the /etc/exports file above
- 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 the v3 server
service rpcbind start
