How to Disable RootSquash on PowerScale NFS Export

Hello Dan Adams,

Have you tried the following steps to disable root squash?

Steps to Disable Root Squash:

1.       Access the export configuration for the desired NFS export.

2.       Modify the export settings to include no_root_squash.

3.       Save the changes to apply the new configuration.

@DELL-Sam L​ I believe I have but please confirm these are correct:

What I've Done:

1. Disabled root mapping (aka rootsquash) via:
   • PowerScale WebUI → Export Settings → "Do not map root users".
2. Confirmed via CLI:
   • isi nfs exports view <export_id> --zone <zone> shows map-root-enabled: false.

have you tried restarting the nfs server and remounting the filesystem on the client?

@DELL-Josh Cr​ Restarting a multi-node PowerScale cluster (or the NFS service) in a production enterprise environment is not really an option lol! I remounted the export on the client to no avail.

What is the output of isi nfs settings global view?

Ensure that the NFSv4 domain on your Linux or Unix client exactly matches the domain on the Isilon cluster.

This is because NFSv4 uses principal strings for authentication, which follow a specific case-sensitive format using a user or group part and a domain part. If the domain strings do not match, OneFS sets the user and group ownership to "nobody" and "nogroup". To correct this, update the domain settings on either the client or the cluster to match the other.

@DELL-Josh Cr​ 

The output is

NFS Service Enabled: Yes
      NFSv3 Enabled: Yes
        NFSv3 RDMA Enabled: No
      NFSv4 Enabled: Yes
              v4.0 Enabled: Yes
              v4.1 Enabled: Yes
              v4.2 Enabled: Yes
     Rquota Enabled: Yes

The alien and server domains match.

What version of onefs are you using?

@DELL-Josh Cr​ 

version 9.7.1.2

Try disabling 4.1 and 4.2 

isi nfs settings global modify --nfsv41-enabled=false --nfsv42-enabled=false

What's the impact of this change on the NFS service in general. especially NFS clients with mounts of other exports on the PowerScale?

It shouldn't affect them unless the client disconnect and reconnect to the share and then they should just connect with 4.0 

Apparently norootsquash works using NFS3 (enforced client-side.) No success using matching NFS4 (with or without matching domains.)

Hi,

Using the CLI (isi commands)

Run this command to modify an existing export 

isi nfs exports modify --id <export_id> --map-root=root

To check the export settings:

isi nfs exports list
isi nfs exports view --id <export_id>

Confirming It’s Disabled

After the change:

1. From your NFS client, mount the export.

2. As root, create a file.

3. Check on the cluster if the file is owned by root, not nobody.

@kamalhinduja​ Thanks for the feedback.  Apparently, I recently discovered I have to force NFS3 mounts after disabling rootsquash on the PowerScale export settings.  No success using  NFS4 (the default on my clients.).