Skip to main content

NFS : Network file system

 


Network file system (NFS):

Its a filesystem developed by sun Microsystem.Inc.

It is a client server system that allows the users to access files accross a network and treat them as if they resided in local file directory.


For example: if you were using a computer linked to second computer via NFS, you could access files on the second computer as if they resided in the directory on the first computer. This is accomplished through the process of exporting (the process by which an NFS server provides remote clients with access to its files) and mounting (the process by which client map NFS shared filesystem)


Steps for NFS configuration on server side:

• Install NFS Packages:

#yum install  nfs-utils  libnfsidmap



once the packages are installed enable and start the NFS services

#systemctl enable rpcbind

#systemctl enable nfs-server

#systemctl start rpcbind

#systemctl start nfs-server

#systemctl start rpc-ststd

#systemctl start nfs-idmapd


>>>>>>>>>>>>>>>>>>>>>>>>>≥>>>>



create NFS share directory and assign permissions

#mkdir /mypretzels

#chmod  a+rwx /mypretzels


 modify/etc/exports file to add new shared filesystem


/mypretzels 192.168.12.7 (rw,sync.no_root_squash) = for only 1 host.


#/mypretzels is the NFS share.

# 192.168.12.7 is the Ip address of client machine. (instead of ip address we can use to share the NFS share with everybody).

# rw is the read write permission to client on NFS share.




• Export the NFS filesystem:

#exportfs  -rv


>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Steps for NFS configuration on client side:

• Install NFS packages:

#yum install nfs-utils rpcbind



 once the packages are installed enable and start rpcbind service:

 #systemctl start rpcbind



make sure firewalld or iptables stopped. (if running)

 #ps -ef | egrep "firewall | iptable"



show the mount from NFS server

#showmount -e 192.168.1.5 (NFS servers ip)



 create the mount point:

#mkdir  /mnt/kramer



mount the NFS filesystem:

#mount   192.168.1.5:/mypretzels    /mnt/kramer (NFS servers ip)


verify mounted filesystem: 

#df-h



 to unmount: 

#umount   /mnt/kramer


Comments

Popular posts from this blog

Linux basic commands

 Linux basic commands: du  -sh  *  |  sort  -h  -r   |  head  -n  40  :    list out first 40 files in the directory that are taking more space in the directory.  cd : change directory Is-l listing the items in long listing format  pwd : print working directory Is-I format: type :no of links:owner : group:size :month :day :time :name cd/: go to/directory whoami: tells us by which username we are logged in. touch jerry: creates the file named jerry in present working directory. cp jerry lex: copy the content of jerry file and paste it to lex file. vi text1: creates the file text1 and open it in vi editor mkdir superman: creates the directory called superman mkdir abc def  : creates 2 folder in one command. touch filename wont work in /etc/ folder if logged in by normal account. man cp: shows manual for cp command. echo "india is my country"> file1 puts the text in file1. rm filename: remove the filename  mv lex luther renames the file from lex to luther  mv luther /h

patching tasks

 Patching a Linux system is a critical task to ensure that the system remains secure, stable, and up-to-date with the latest features and fixes. Here’s a comprehensive guide to the tasks involved in Linux patching: 1. Pre-Patching Preparation Backup System : Ensure you have a full system backup, including critical data, configuration files, and applications. Test the backup to verify its integrity. Check Disk Space : Verify that you have enough disk space, particularly on /var , /tmp , and /boot partitions. Review Current Patch Level : Determine the current patch level and installed packages using package management tools like yum , apt , dpkg , or rpm . Check System Logs : Review system logs to identify any issues that might affect the patching process. Test in a Staging Environment : If possible, apply patches in a staging environment that mirrors production to identify potential issues. Notify Stakeholders : Inform stakeholders about the scheduled maintenance window and expected do