There is a difference between your working and non-working idmapd.conf: The working does not have: [Translation] Method = nsswitch That may be what's catching you up. Frank > This is a followup to a previous post I made. > > With Frank Filz's helpful suggestions I was able to gather better data. > > problem: when using chown as root on a nfs4 filesystem on newer linux > releases file owners get sets to nobody. > the user type doesn't seem to matter (/etc/passwd, LDAP, Samba4) > > setup: Server is FreeBSD 10 system with NFSv4 share. > Server and clients are all configured with the same idmap domain > Network users have consistent uid/gid on server and clients > clients with older linux releases work OK (Ubuntu 12.04, CentOS 5 and 6) > clients with newer linux releases do not work ( Fedora 20, Ubuntu 14.04, > Mint 16 ) > > clues: > > 1. working and non-working systems get to the same fchownat() system call > with the same arguments (via strace). > > example (identical on working and non-working client): > ... > fchownat(AT_FDCWD, "/mnt/test", 11111, 4294967295, 0) = 0 > close(1) = 0 > close(2) = 0 > close(4) = 0 > exit_group(0) = ? > +++ exited with 0 +++ > > 2. working system sends NFSV4 SETATTR request with owner set to: > matlab@xxxxxxxxx and non-working as 11111 (via wireshark) -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
