The NFSv4 server could not look up the user or group name to map to a user id (UID) or group id (GID).

Administrator action

NFSv4 uses the string 'user@domain' instead of numeric UIDs and GIDs. This event occurs if there is a mismatch between the client domain name and the NFSv4 server domain name, or if the user database configuration is incorrect.

For example, the domain name stored in the idmap.conf file on the client might not match the NFSv4 domain name of the cluster (vfs.nfsrv.nfsv4.domainname).

  1. Verify that the idmap.conf file is not missing or corrupted on the client.
  2. Compare the value for domainstring in the idmap.conf file and the value for the cluster NFSv4 domain name that is returned from the following cluster sysctl command:
    isi_for_array -s sysctl vfs.nfsrv.nfsv4.idmap_replacedomain
  3. If these values are different, update the idmap.conf file to match the domain of the cluster. Alternatively, you can match the domainstring and the value for the NFSv4 domain name of the cluster in the two files by running the following sysctl command:
    isi_sysctl_cluster vfs.nfsrv.nfsv4.idmap_replacedomain=1
  4. Verify that Active Directory, NIS, and LDAP servers are configured correctly.

If the event persists, gather logs, and then contact EMC Isilon Technical Support for additional troubleshooting. For instructions, see Gathering cluster logs.