Skip to main content

How to configure Network file system (NFS) client?

By
68.How to configure Network file system (NFS) client?
Ans.
1. To configure client, make sure that the portmapper, NFS file locking daemons statd & lockd, mount command are avaialbe.

 2. NFS client needs the portmapper running in order to process and route RPC calls and returns from the server to the appropriate port and programs.

 3. We can ensure portmapper is running or not by using following command:
#service portmap status

 4. If portmapper is not running then it’ll show us portmapper is stopped to start portmapper we’ll use following command:
#service portmap start

 5. Mounting can be done using following commands:
For example we wants to mount /media from the server configured at the end then we’ll execute following commands:
#mount –t nfs 192.168.166.5:/media /media

 6. If user wish, he/she can specify client mount options using mounts arguments as;
#mount –t nfs 192.168.166.5:/media /media -o resize=8292,wsize=8192, hard, nolock

 7. Following are the mounting options:
bg – Enables mount request to run in the background if first fails
fg – Enables mount request to run in the foreground if first fails
hard – Enables client to continue retrying if server does not respond
soft – Enables client operation to fail and terminate
tcp – Declares protocol to be tcp
udp – Declares protocols to be udp
resize=n – Declares read size of clients buffer
wsize=n – Declares write size of clients buffer
retry=n – Enables n retries for mounting
intr – Enables ctrl+c to work as interrupt
lock – Starts nfs locking via statd and lockd
nfsvers=n – Specifies versions of nfs
port=n – specifies nfs server port for connection

Labels:

Comments

Post a Comment

Popular posts from this blog

Java,ES,QT practical files

By
All practical files: Click below to start download Uploaded on special request||||
2 comments
Read more

How to configure Network file system version 4 (NFSv4) client?

By
69.How to configure Network file system version 4 (NFSv4) client? Ans. 1. There are two new options listed in NFSv4 are introduced as: clientaddr and ports 2. The version 3 of NFS introduced NFS over TCP, which improved NFS’s reliability. 3. In NFSv3, users use the mount option i.e., tcp as client whether client wants to use TCP or UDP to communicate with the server. NFSv4 replaces tcp or udp with a single option i.e. ports=tcp or udp 4. The default buffer size for NFSv4 is 8192 bytes, but it can grow to as large and by 32,678 bytes, which results performance improvements. 5. Following are the mount options: clientaddr=n – Declares client to be multihomed proto=type – Declares port as either udp or tcp resize=n – declares read size of clients buffer wsize=n – Declares write size of clients buffer sec=mod – Declares security model as either krb, krb5 etc.
Post a Comment
Read more

Absolute Links vs. Relative Links – SEO Value

By
Absolute Links vs. Relative Links – SEO Value The debate between  absolute links and relative links  continues to live on in the SEO world. The individual significance of each has been contested, but it is widely regarded that absolute links provide better SEO value on the whole than relative links. Many believe that absolute links have less potential for getting messed up when search engines index your page. It shouldn’t really make a difference, but many conclude that this is reason enough. Read more...
Post a Comment
Read more