Knowledge Base

Symptoms

The customer is unable to use the umask command in an NFS shared folder, and the command does not seem to work as expected.

Possible Causes

The issue might be due to Advanced ACL being enabled for the volume, which can cause compatibility problems with Linux NFS.

Solution

• Check if Advanced ACL is Enabled
  1. Verify whether Advanced ACL is enabled on the volume.
  2. If it is enabled, re-create the volume and disable Advanced ACL. Advanced ACL can cause compatibility issues with Linux NFS.
• Check the umask Setting
  1. Ensure that the umask is correctly set in the environment where it is expected to work.
  2. Run the following command in the terminal to view the current umask setting:
     
• Verify NFS Mount Options
  1. NFSv3 vs. NFSv4: NFSv3 does not support ACLs natively and might handle file permissions differently compared to NFSv4.
  2. File System Mount Options: Ensure that the NFS share is mounted with the appropriate options. For example, the acl option should be enabled if you are working with POSIX ACLs.
  3. Check the /etc/fstab file or the mount command used for the NFS share to ensure it includes the correct options.
• Server-Side Configuration
  1. NFS Server Export Options: Review the NFS server’s export configuration (typically in /etc/exports) to ensure it is not overriding permissions or enforcing settings that conflict with the client’s umask.
  2. For instance, options like all_squash or root_squash might affect permissions.
• Check ACLs (Access Control Lists)
  1. If ACLs are used on the NFS share, they might override the umask settings.
  2. Use the getfacl command to inspect the ACLs on the directory or file:
     
  3. If ACLs are present and enforce specific permissions, they might prevent the umask from applying as expected.
• Client-Side Permissions and Settings
  1. User Permissions: Ensure that the user setting the umask has sufficient permissions to apply it.
  2. Profile Configuration: If the umask is set in a shell profile (such as .bashrc or /etc/profile), verify that it is being executed correctly. Check for syntax errors or conflicting settings that might override the umask.

• Check for NFS Version Issues

  1. Differences between NFS versions might affect umask behavior. For example, NFSv3 handles permissions differently than NFSv4.
  2. Consider upgrading to NFSv4 if using NFSv3 and facing permission-related issues.
• Test on Local File System
  To rule out NFS-specific issues, test the umask behavior on a local file system. If umask works correctly on the local file system but not on the NFS mount, the issue is likely related to NFS configuration or interaction between umask and NFS.
• If the Problem Persists
  If the issue remains unresolved after following these troubleshooting steps, open a support ticket at Infortrend Support. Provide details including the problem symptoms, the umask command and its results, and diagnostic logs exported from the web GUI.