vSAN File Services : GID of created files is changed to 99

Products

• VMware vSAN

Issue/Introduction

• Files and directories created on an NFS share provided by vSAN File Services are assigned a GID of 99, even when the expected GID is 0.
• The login user has GID 0 and there is no group with GID 99 configured on the NFS client OS.
  
  

Environment

vSAN File Services

Cause

When the Root squash option is enabled, GID 0 is treated as part of the privileged root identity. Consequently, any file creation request originating from a user with GID 0 is subject to the squash policy, which maps the group ID to an anonymous/nobody GID (such as 99 or 4294967294) to ensure security.

Resolution

To resolve this issue, perform one of the following actions:

• Modify the user GID: Change the primary GID of the user from 0 to a non-zero value (e.g., 1001). This ensures the user is no longer subject to the root squash policy.
  
  
• Disable root squash: If the security policy allows, disable the Root squash setting for the specific file share in the vSAN File Service configuration.

Additional Information

"Operation not permitted" error occurs on vSAN File Service when changing NFS4 share ownership