In this guide, we explore how the Network File System (NFS) differs from block device storage. Unlike block devices that manage data in blocks, NFS stores data as individual files, offering a unique file-centric approach to network storage. NFS utilizes a server-client model to share directories seamlessly across the network. For instance, consider a software repository server that maintains a directory atDocumentation Index
Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
Use this file to discover all available pages before exploring further.
/software/repos. By exporting this directory using NFS, employee laptops can access its contents as if the files were stored locally—even though they reside on the server.

In NFS terminology, “exporting” refers to the process of sharing a directory with client systems.
/etc/exports. This file specifies which clients are permitted to access the shared directories. For example, if the allowed client IP addresses are 10.61.35.201, 10.61.35.202, and 10.61.35.203, and the NFS server has an IP of 10.61.112.101, the configuration in /etc/exports might look like this:
/etc/exports file on the server, apply the changes and share the directories using the exportfs command. To export all the mounts defined in the exports file, use:
/mnt/software/repos), use the following command, ensuring that you specify the NFS server’s IP (or hostname) followed by the exported directory separated by a colon:
While there are several advanced options available with the
exportfs command, the examples provided above cover the fundamentals necessary to get started with NFS.