_netdev

(I tried this case study on Almalinux 9 and Almalinux8)

I am very curious administrator and I like logical during the system.

Today I will explain you some "little hint" about nfs connection.

First;

What is NFS?

NFS is not need for speed ;-)

NFS is network file system.

We have the first system (which is installed NFS server)

We have the seceond system (which is installed NFS Client)

As you know, the client-server architecture is not new for you.

Ok: installation on server and client:

1)   

168   yum install nfs-utils -y
  169  vi /etc/exports
  170  mkdir /nfs
  171  chmod 777 /nfs
  172  exportfs -a
  173  systemctl enable --now {rpcbind,nfs-server,rpc-statd,nfs-idmapd}
  174  showmount -e localhost
  175  ls /nfs
  176  systemctl status firewalld
  177  ip a
  178  systemctl stop firewalld
  179  history

  (the numbers are from history of commands and I stopped firewalld)
 
2)  (of course bad IP )


53  yum install nfs-utils -y
   54  mkdir /mnt/nfs
   55  showmount -e 9.8.900.3111
   56  vi /etc/fstab
   57  mount -a
   58  systemctl daemon-reload
   
3) What is  in /etc/fstab in nfs way?


9.8.900.3111:/nfs /mnt/nfs nfs rw,hard,intr,rsize=8192,wsize=8192,timeo=14,_netdev 0 0

rw = read and write

hard= - when nfs connection is fail, NFS request weill be retried.

intr = interupt - the nfs fail - request process will be interrupted

rsize = read request

wsize = write request

timeo= - in our case: nfs client is waiting 14 seconds to answer for nfs server before reply NFS request

_netdev = when the nfs client has not work with network (during the reboot ) - server will be booted and not mounted the NFS  

_netdev

please read this article: https://linuxopsys.com/topics/linux-nfs-mount-entry-in-fstab-with-example  (very well explain)