Description of problem:

An operation like 'chown' creates requests which do not respect the settings in /etc/idmapd.conf.  E.g. my /etc/idmapd.conf is

----
[General]
Verbosity = 0
Domain    = SIGMA-CHEMNITZ.DE

[Mapping]
Nobody-User  = nobody
Nobody-Group = nobody

[Translation]
Method = nsswitch
----

Userspace uid/gid translation is done by nslcd (LDAP).  When there is done

 chown 505 ~/foo

an SETATTR request with an FATTR4_OWNER of 'ensc.de' is issued.  Because the NFS4 domain is SIGMA-CHEMNITZ.DE, this operation will fail.

Strange thing is, that rpc.idmapd will be called for unknown (--> nobody mapping) users only.  E.g. 'strace -f -p <pidof-idmapd>' shows no activity for 'chown <valid-uid>' operations but for invalid uids only.  I see a connection to 'nslcd' during the chown(2) syscall but can not determine the source ('netstat' reports pid 0).

GETATTR responses from the server are containing expected owner values like 'ensc' which are mapped correctly on the client.


Server is an RHEL6 machine, client an F17 one (F16 was fine). Shares are mounted by 

...:/home/ /home nfs4 comment=systemd.automount,exec,nodev,nosuid,rw,sec=krb5i,posix,nointr



Version-Release number of selected component (if applicable):

nfs-utils-1.2.6-0.fc17.x86_64
kernel-3.3.7-1.fc17.x86_64