Configure NFS exports fsid on Linux with clear commands, unique IDs, and multiple network support for stable file sharing. Our Live Support Team is always here to help you.
How to Configure NFS Exports FSID on Linux Like a Pro
Setting up NFS exports fsid correctly is crucial for stable file sharing across Linux networks. Without properly assigned FSIDs, your NFS server may behave unpredictably, especially when 
multipledirectories or subnets are involved. Here’s a clear, practical guide that covers everything you need, including NFSv4 pseudo roots, multiple networks, and GPFS file systems.
On Linux, a file system cannot be exported via NFSv4 unless it supports POSIX ACLs. After editing the /etc/exports file, always run:
exportfs -raThis command forces the system to reread the exports file and apply any changes immediately.
An Overview
Assigning FSID for GPFS File Systems
1. Single Directory Export Example
Starting with Linux kernel 2.6, each GPFS file system exported on NFS must have a unique fsid. For example, exporting /gpfs/dir1 looks like:
/gpfs/dir1 cluster1(rw,fsid=745)FSID values must remain unchanged after reboots (NFS Error: FileID Changed). Always unexport a file system before modifying its fsid.
2. Multiple Directories Within the Same File System
You can export multiple directories within a single file system, but each requires a distinct fsid:
/gpfs/dir1 cluster1(rw,fsid=745)
/gpfs/dir2 cluster1(rw,fsid=746)3. Consistency Across Multiple Nodes
If a GPFS file system is exported from several nodes, fsids must remain consistent on all nodes to prevent conflicts.
Configuring Pseudo Root for NFSv4
Creating Pseudo Root and Bind Mounts
NFSv4 requires a pseudo root. To configure directories for export:
mkdir -m 777 /export /export/dir1 /export/dir2
mount --bind /gpfs/dir1 /export/dir1
mount --bind /gpfs/dir2 /export/dir2These bind mounts must be unmounted after GPFS stops:
umount /export/dir1; umount /export/dir2and bind-mounted again once GPFS restarts.
Updating /etc/exports File
The /etc/exports file must include the pseudo root with fsid=0 and each directory’s fsid:
/export cluster1(rw,fsid=0)
/export/dir1 cluster1(rw,fsid=745)
/export/dir2 cluster1(rw,fsid=746)Mounting and Unmounting After GPFS Restart
This approach allows NFSv4 to identify a base directory under which all exported directories reside, maintaining proper access control.
Setting Up FSID for Multiple Networks
Exporting to Multiple Subnets Separately
To allow multiple networks to mount a directory, list each subnet on separate lines:
/opt/dir1 192.168.1.0/24(rw,sync)
/opt/dir1 10.10.0.0/22(rw,sync)Exporting to Multiple Subnets on a Single Line
Alternatively, list multiple subnets on a single line with repeated mount options:
/opt/dir1 192.168.1.0/24(rw,sync) 10.10.0.0/22(rw,sync)Maintaining Consistent FSID Across Subnets
When using fsid, ensure it is the same for all network entries, and always consider encryption in transit for secure network access:
/opt/dir1 192.168.1.0/24(rw,sync,fsid=1)
/opt/dir1 10.10.0.0/22(rw,sync,fsid=1)or
/opt/dir1 192.168.1.0/24(rw,sync,fsid=1) 10.10.0.0/22(rw,sync,fsid=1)Inconsistent fsids can lead to slow server failures over time.
Best Practices for NFS Exports FSID
1. Avoiding Inconsistent FSID Errors
Always assign unique fsids and keep them consistent across exports and nodes. Unexport before making changes to prevent server issues.
2. Ensuring Stable and Secure NFSv4 Exports
Using pseudo roots and bind mounts simplifies NFSv4 exports while improving security. It prevents clients from accessing unintended directories and allows easier server-side access control.
[If needed, Our team is available 24/7 for additional assistance.]
Conclusion
Properly configuring NFS exports fsid is essential for reliable Linux file sharing. By assigning unique fsids, maintaining consistency across nodes, and using pseudo roots with bind mounts, administrators can ensure stable, secure, and predictable NFSv4 exports. Following these practices prevents server slowdowns, supports multiple networks efficiently, and keeps your file systems organized. Implementing these guidelines provides confidence in network storage management while minimizing errors and downtime.
