Topics Summary

 

How NFS works?

Whenever we installed the packages for configuring the nfs client and server the daemons for both client and server will active in order to work on nfs.

The client side daemons are lockd and statd.

The server side daemons are nfsd, mountd, rquotad.

Each and every daemon has its own significance. Let us know about daemons more lucidly.

 

Rpc.nfsd:

This daemon handles the client side requests. It works with the Linux kernel to meet the dynamic demands of NFS clients such as providing server threads each time an NFS client connects. This process corresponds to the nfs service.

 

Rpc.mountd:

This process is used by nfs server to process the mount requests from the nfs clients. This checks that the requested file system is shared to the particular client or not. If that is shared it allows the client to mount that file system remotely.

 

Lockd:

Lockd is the thread which runs on both servers and clients. This allows the clients to lock the files in the servers.

 

Rpc.statd:

This process notifies the nfs clients when an nfs server is restarted without gracefully down. It doesn’t need user configuration. This is not used in nfs4.

 

rpc.rquotad:

This process provides user quota information for remote users. rpc.rquotad is started automatically by the nfs service and does not require user configuration.

 

Basic Working of NFS client-server:

working of nfs

 

  • In the above diagram the client requests to mount the file system from the server through the command.
  • The server will listen that command at port number 2049.
  • The mountd daemon starts working in the server and checks weather the client is authorized to mount the shared file system.
  • Mountd checks for the client in hosts.allow and hosts.deny files to confirm the client is authorized or not.
  • If client is authorized the file system is mount at client otherwise it shows access denied.