https://bugzilla.novell.com/show_bug.cgi?id=813641
https://bugzilla.novell.com/show_bug.cgi?id=813641#c16
--- Comment #16 from Randall Smith 2013-08-01 23:04:33 UTC ---
Just to clarify, our NFSv4 id mapping issue is identical to flo gleixner's
original submission; the rpc.idmapd verbose output looks identical. We also
employ ldap so our /etc/nsswitch.conf directs lookups to ldap.
Does your request for traces and logs suggest that NFSv4 id mapping should work
with older NFSv4 clients like OpenSuse 11.x and Ubuntu 11.x? For example, is
compatibility expected between nfs-utils-1.2.7-2.10.1 and
nfs-utils-1.2.3-11.16.1?
Here are a few observations:
After killing rpc.idmapd on both our OpenSuSE 12.3 NFSv4 server and our
OpenSuSE 12.1 NFSv4 client, we find that ls -l shows that uid and gid are still
correctly mapped to names on the client. However for the case of an OpenSuSE
11.4 NFSv4 server and an OpenSuSE11.4 NFSv4 client, just killing rpc.idmapd on
the client, ls -l shows the uid and gid unmapped as 4294967294.
With rpc.idmapd running on the client and server, and after several exchanges
with both 12.1 and 11.4 clients, the contents of
/proc/net/rpc/nfs4.nametoid/content on the OpenSuSE 12.3 server has only the
header "#domain type name [id]". The same goes for nfs4.idtoname/content.
A network trace on the 11.4 client reveals that the V4 REPLY to a V4 LOOKUP
contains (correct) numeric UID and GIDs for the fattr4_owner and
fattr4_owner_group attributes.
Would you still like me to send in a network trace and the rpc.idmapd outputs?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.