Reasons for ID Mapping to Fail

The following situations can cause ID mapping to fail:

• If the user or group that exists in an ACL entry on the server cannot be mapped to a valid user or group on the client, the user is not allowed to read the ACL on the client.

  For example, when you issue the ls -lv or ls -lV command, you receive the error message, Permission denied,for the files with user or group ID ACL entities that cannot be mapped from the server to the client. The ID mapper was unable to map a user or group in the ACL. If the ID mapper had been able to map the user or group, a plus (+) sign would have appeared after the permissions in the files list that is produced by ls -l. For example:

  % ls -l -rw-r--rw-+ 1 luis staff 11968 Aug 12 2005 foobar

  Similarly, the getfacl command can return the Permission denied error message for the same reason. For more information about this command, see the getfacl(1) man page.

• If the user or group ID in any ACL entry that is set on the client cannot be mapped to a valid user or group ID on the server, the setfacl or the chmod command can fail and return the Permission denied error message.

• If the client and server have mismatched NFSMAPID_DOMAIN values, ID mapping fails. For more information, see Keywords for the /etc/default/nfs File.