Skip to main content

Step-by-Step Guide to Create and Attach an NFS Mount Point to a New Server

Step-by-Step Guide to Create and Attach an NFS Mount Point to a New Server


Prerequisites:

  1. NFS Server: A server with NFS (Network File System) installed and configured to export the directory.
  2. Client Server: The server where the NFS mount point will be attached.
  3. Network Connectivity: Ensure both servers can communicate over the network.

Steps on the Source NFS Server where the storage is present

1. Install NFS Utilities


sudo yum install -y nfs-utils # For Red Hat-based systems sudo apt-get install -y nfs-kernel-server # For Debian-based systems

2. Create the Directory to Export


sudo mkdir -p /mnt/shared

3. Set Permissions for the Directory


sudo chmod 777 /mnt/shared

4. Edit the Exports File

Add the directory to /etc/exports with the appropriate permissions:


sudo nano /etc/exports

Add the following line to export the directory:


/mnt/shared *(rw,sync,no_root_squash)
  • rw: Read-write access.
  • sync: Synchronize changes immediately.
  • no_root_squash: Allows root on the client to act as root on the NFS server.

5. Export the Directory

Run the following command to make the changes effective:


sudo exportfs -rav

6. Start and Enable the NFS Service


sudo systemctl start nfs-server sudo systemctl enable nfs-server

Steps on the Client Server

1. Install NFS Utilities


sudo yum install -y nfs-utils # For Red Hat-based systems sudo apt-get install -y nfs-common # For Debian-based systems

2. Create a Mount Point


sudo mkdir -p /mnt/nfs_shared

3. Mount the NFS Share Temporarily

Use the mount command to mount the NFS share:


sudo mount -t nfs <NFS_SERVER_IP>:/mnt/shared /mnt/nfs_shared

Replace <NFS_SERVER_IP> with the IP address of the NFS server.

4. Verify the Mount

Check if the NFS share is mounted:


df -h

You should see the NFS share listed as /mnt/nfs_shared.


Persist the Mount Across Reboots

  1. Open the fstab file:


    sudo nano /etc/fstab
  2. Add an entry for the NFS share:


    <NFS_SERVER_IP>:/mnt/shared /mnt/nfs_shared nfs defaults 0 0
  3. Save the file and exit.

  4. Test the fstab entry by unmounting and remounting all filesystems:

    sudo umount /mnt/nfs_shared sudo mount -a

Verification

  1. Test writing and reading files on the mount point:


    sudo touch /mnt/nfs_shared/test_file ls -l /mnt/nfs_shared/
  2. Ensure the file appears on both the NFS server and client.


Troubleshooting

  1. Firewall:

    • Ensure the required NFS ports are open:

      sudo firewall-cmd --add-service=nfs --permanent sudo firewall-cmd --add-service=rpc-bind --permanent sudo firewall-cmd --add-service=mountd --permanent sudo firewall-cmd --reload
  2. SELinux:

    • Allow NFS through SELinux:

      sudo setsebool -P nfs_export_all_rw 1







Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...