PowerScale

Creating NFS Shares in Dell EMC Isilon OneFS (Step-by-Step)

Manoj Patel
Dell EMC PowerScale Isilon rack server for NFS export configuration

Setting up Network File System (NFS) storage on enterprise scale-out NAS arrays is a fundamental task for storage administrators. Knowing how create NFS share in Isilon environments enables Linux enterprise servers, virtualisation clusters, and high-performance computing (HPC) workloads to connect to scalable file storage seamlessly.

In Dell EMC PowerScale OneFS (formerly Isilon OneFS), file sharing across UNIX and Linux environments is accomplished through flexible export policy rules. Whether you are expanding an enterprise data repository or setting up persistent volumes for containerised workloads, this step-by-step tutorial walks you through configuring NFS exports using both the OneFS Web Administration Interface and the command-line interface (CLI).

Understanding NFS Exports on Dell EMC Isilon OneFS

Before diving into the configuration steps, it is essential to clarify a terminology distinction that often confuses administrators coming from Windows storage background. On Dell EMC PowerScale OneFS systems, file shares exposed to Linux/UNIX hosts using the NFS protocol are formally referred to as NFS Exports rather than SMB “shares”. While Windows storage relies on SMB shares, Linux systems mount directories exported through the NFS daemon.

An NFS export configuration in OneFS links an underlying path on the distributed `/ifs` file system with client access policies. Unlike monolithic storage systems, OneFS distributes file data across all nodes in the cluster. When a client connects to an NFS export using a SmartConnect zone name, OneFS automatically balances client connections across node interfaces to ensure high availability and optimal throughput.

Dell EMC Isilon OneFS manages NFS connections at the cluster level, exposing directory trees under `/ifs` through configurable NFS exports rather than standard storage shares.

OneFS supports NFSv3, NFSv4, and security protocols like Kerberos. Establishing precise directory paths, client IP boundaries, and user mapping policies during export creation ensures data integrity and security across your enterprise network.

What You Will Need Before Creating an NFS Share

To successfully complete this guide, verify that you have the following prerequisites in place:

  • An active Dell EMC Isilon or PowerScale cluster running OneFS 8.x, 9.x, or later.
  • Administrative credentials (e.g., `root` or an account with `ISI_PRIV_NFS` privileges).
  • A target directory created under `/ifs` (e.g., `/ifs/data/finance_nfs`).
  • Network details including client IP addresses, subnet masks, or CIDR blocks allowed to access the export.
  • A configured SmartConnect zone name (e.g., `isilon-nfs.example.com`) for client DNS load balancing.
  • A Linux client system with `nfs-utils` or `nfs-common` installed for testing and mounting.

If you regularly perform CLI-based management tasks across clusters, review our guide on configuring passwordless SSH authentication on Isilon to streamline administrative workflows.

Step 1: Access the OneFS Web Administration Interface

Log into your OneFS cluster management node using a web browser. Open your browser and navigate to the management IP or Fully Qualified Domain Name (FQDN) of your cluster:

https://<cluster-mgmt-ip>:8080

Enter your administrative username and password. Once authenticated, you will arrive at the OneFS dashboard. From the top navigation menu, navigate to Protocols > UNIX Sharing (NFS) > NFS Exports.

This screen displays all active NFS exports across the cluster, along with their export IDs, paths, and client descriptions. To begin setting up a new export, click the Create an Export button located in the top right corner.

Step 2: Configure Directory Paths and Export Names

Specify where your data resides within the distributed `/ifs` file system structure. In the Create an NFS Export window, locate the Directory Paths section:

  1. Directory Path: Enter the absolute directory path on the Isilon cluster. For example, `/ifs/data/finance_nfs`. If the directory does not yet exist, check the option to automatically create the directory path during creation.
  2. Description: Enter a clear descriptive label (e.g., `Finance Department Shared Storage`) to simplify future administrative audits.
  3. Encoding: Select `UTF-8` (default) to ensure full compatibility across modern Linux distributions and file encoding standards.

Always ensure directory paths reside under `/ifs` — creating exports outside the distributed path will result in path resolution failures across cluster nodes.

Step 3: Define Access Controls and Security Settings

Setting up access permissions prevents unauthorized reads or modifications. OneFS provides granular controls over read-only and read-write permissions:

  • Read-Write Clients: Specify clients or subnets that require full read, write, and execute permissions.
  • Read-Only Clients: Specify hosts that only require read access (such as backup agents or reporting servers).
  • All Clients / Default Access: Select default permissions (Read-Only or Read-Write) for any client matching the export rules.

In enterprise environments, explicit host controls are recommended over wildcard access. According to the official Dell PowerScale OneFS NFS Design Considerations and Best Practices guide, restricting exports to specific subnets prevents network exposure and unauthorized mounts.

Step 4: Configuring Client IP Restrictions and Root Squashing

Security is a key requirement when configuring NFS storage. Without proper mapping, remote `root` users on client machines could claim superuser privileges on your storage array.

In the Client Settings and User Mapping options, configure root squashing settings:

  • Clients / Host Restrictions: Enter individual client IP addresses (`192.168.10.50`), IP ranges (`192.168.10.50-192.168.10.100`), or subnet CIDR notation (`192.168.10.0/24`).
  • Map Root Users (Root Squashing): Enable root mapping to prevent remote `root` accounts from having unconstrained access on the cluster. Select Map root to user and specify `nobody` or User ID (UID) `65534` (Group ID `65534`).
  • Map Unmapped Users: Map any unrecognized client UIDs to `nobody` or a designated non-privileged service user to enforce least-privilege security.

Mapping remote root users to UID 65534 (nobody) closes critical security vulnerabilities, ensuring guest client accounts cannot overwrite core cluster configurations.

After defining these rules, click Save / Create Export. OneFS commits the changes instantaneously without requiring an NFS service restart.

Step 5: Create the NFS Share via CLI (Alternative Method)

For storage administrators who prefer command-line speed or automation scripts, OneFS provides the powerful `isi` utility. You can execute the entire export creation process in a single command using `isi nfs exports create`.

SSH into your Isilon cluster as `root` or an administrative user, then execute the following command:

isi nfs exports create \
  --paths=/ifs/data/finance_nfs \
  --clients=192.168.10.0/24 \
  --read-write-clients=192.168.10.0/24 \
  --map-root-enabled=true \
  --map-root-user=nobody \
  --description="Finance Department NFS Export"

To verify that your new export has been successfully created via CLI, run:

isi nfs exports list

To view detailed settings for the specific export ID (e.g., Export ID `12`), run:

isi nfs exports view 12

If you automate repetitive storage provisioning workflows across multiple systems, compare this method with creating NFS exports on NetApp ONTAP SVMs or explore automating OneFS operations with the Isilon REST API.

Step 6: Mount and Validate the NFS Share on Linux Clients

Now that the NFS export is active on your Isilon cluster, test connectivity and access from a Linux client machine.

First, log into your Linux terminal and install the required NFS client utilities if they are not already installed:

# RHEL / CentOS / Rocky Linux
sudo dnf install -y nfs-utils

# Ubuntu / Debian
sudo apt-get update && sudo apt-get install -y nfs-common

Next, test export visibility from the client using `showmount`. Replace `isilon-nfs.example.com` with your cluster’s SmartConnect zone name or IP address:

showmount -e isilon-nfs.example.com

You should see your newly created export listed:

Export list for isilon-nfs.example.com:
/ifs/data/finance_nfs 192.168.10.0/24

Create a local mount point on the Linux client and execute the mount NFS share Linux command:

sudo mkdir -p /mnt/finance_share
sudo mount -t nfs -o rw,hard,intr isilon-nfs.example.com:/ifs/data/finance_nfs /mnt/finance_share

Validate the mount status and write permissions by creating a temporary file:

df -h /mnt/finance_share
sudo touch /mnt/finance_share/test_file.txt
ls -la /mnt/finance_share/test_file.txt

To make this mount persistent across Linux server reboots, append the following line to your `/etc/fstab` file:

isilon-nfs.example.com:/ifs/data/finance_nfs  /mnt/finance_share  nfs  rw,hard,intr,_netdev  0 0

Troubleshooting Common Isilon NFS Share Issues

Even with precise steps, storage configurations can run into connectivity hurdles. Here are common issues encountered when deploying NFS exports on OneFS and how to resolve them quickly:

  • Permission Denied (EACCES / EPERM): This typically occurs when client IP addresses or netmasks do not match the export client list. Verify that your host IP falls strictly within the configured CIDR subnet (`/24` vs `/32`). Additionally, check directory permissions on the underlying `/ifs` path using `isi chmod` or standard POSIX permissions.
  • RPC Timeout / Connection Timed Out: Usually caused by network firewall rules blocking NFS traffic. Ensure TCP and UDP ports `2049` (NFS), `111` (portmapper), and `300` (mountd) are open between client subnets and the SmartConnect pool IP range.
  • SmartConnect DNS Resolution Failures: If `showmount` fails using the domain name but works using a direct node IP, verify that client `/etc/resolv.conf` points to a DNS server delegating the SmartConnect zone to Isilon’s SIP (SmartConnect Service IP).
  • Stale File Handle Errors: Occurs when an export is modified or deleted while clients hold open mounts. Remount the share on the client using `mount -o remount` or unmount with `umount -f /mnt/finance_share`.

Key Takeaways and Post-Configuration Best Practices

Following industry standards ensures high-performance file access and robust data protection across your OneFS environment:

  • Leverage SmartConnect: Always mount NFS exports using a SmartConnect DNS name rather than a static node IP address to distribute client sessions evenly across cluster interfaces.
  • Always Enforce Root Squashing: Map root accounts to UID `65534` (`nobody`) to preserve security boundaries between Linux client administrators and cluster storage.
  • Monitor Subnet Boundaries: Double-check client host definitions during creation — accidental wildcard entries (`*`) expose storage paths to entire corporate networks.
  • Automate with CLI or API: Use `isi nfs exports create` or OneFS REST APIs for scalable, repeatable deployments during environment rollouts.

Conclusion

Understanding how create NFS share in Isilon systems allows storage administrators to deliver reliable, high-performance file services for enterprise Linux environments. By following the WebUI or CLI workflows outlined in this guide — and enforcing root squashing and SmartConnect load balancing — you establish a resilient, secure storage layout backed by Dell EMC PowerScale OneFS.

Related Posts