https://bugzilla.novell.com/show_bug.cgi?id=810408 https://bugzilla.novell.com/show_bug.cgi?id=810408#c0 Summary: Back version NFS client sees files owned by nobody:nobody Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: qa-bugs@suse.de Found By: Customer Blocker: --- Created an attachment (id=530536) --> (http://bugzilla.novell.com/attachment.cgi?id=530536) /etc/idmapd.conf on client and server I have some NFS servers newly upgraded to OpenSuSE-12.2 (nfs-kernel-server-1.2.6-2.12.1.i586 and x86_64) and clients with v11.4 (nfs-client-1.2.3-11.16.1.i586 and x86_64). The NFS protocol is the default, which is NFSv4, and security is the default, which is sec=sys. The clients see NFS mounted files owned by nobody:nobody. Other version combinations work normally, that is, the files are seen with their correct owner and group. 1.2.3 mounting 1.2.3; 1.2.6 mounting 1.2.3; 1.2.6 mounting 1.2.6 all work; only 1.2.3 mounting 1.2.6 fails. This patch notice: http://comments.gmane.org/gmane.linux.nfs/46028 alleges that with the default setting of nfs4_disable_idmapping =1, back-version clients should successfully interoperate with recent servers, but my experience is that they fail equally with this parameter set explicitly to 1, to 0, or unset (on the 1.2.6 server). This is for module nfsd.ko on the server; nfs,ko also has this parameter but it's irrelevant to this bug. The 1.2.3 clients don't have this parameter. Workaround: No forum posting that I ever saw reported a solution for the NFSv4 mounting problem. However, see this thread: http://forums.opensuse.org/english/get-technical-help-here/network-internet/... (OP is omattiaso, dated 2013-01-24). Knurpht recommends a scorched earth solution: reverting to NFSv3. To do that, edit /etc/nfsmount.conf, uncomment and alter the setting: Nfsvers=3. This fixed it for omattiaso and fixed it for me. What I would like the developers to do: Figure out why the promise of interoperability is not delivered on, and tell us how to get a back-version client to mount from a modern server using NFSv4. Appendix: Questions about misconfiguration often asked in forum postings: * Are your numeric and alphabetic UID/GIDs in sync on the client and server? Yes, identical /etc/passwd and /etc/group for system entities, and NIS for ordinary users. * Is rpc.idmapd actually running? Yes, and its debug mode reports successful or failing ID translations as the case may be. * Did the translation cache get cleared? According to the source code, rpc.idmapd attempts to do so on startup, but I was suspicious that it wasn't really happening so I rebooted the client and server after most configuration changes. * What is the error message? On the client: nss_getpwnam: name '520' does not map into domain 'localdomain' (this file was owned by an ordinary user.) * Does /etc/idmapd.conf specify the domain explicitly and the same on the client and the server? Yes, Domain = localdomain. Actually I was never able to get evidence that it was obeying the domain in /etc/idmapd.conf, though other users' reports suggest that it was obeyed for them. * Specifying things explicitly: it didn't help to specify the default [Translation] Method = nsswitch, nor the default sec=sys in /etc/exports. * How do you know the NFS protocol? /proc/mounts shows it. -- 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.