Dear Steve, Thank you for your interest in the matter. It's cost me precious time, so all help is greatly appreciated. Many thanks!
I've now checked my nfs-common config, it had the following relevant bits: # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD=yes ... # Do you want to start the idmapd daemon? It is only needed for NFSv4. NEED_IDMAPD=yes GSSD is turned off by default, and I hope it has nothing to do with this bug. For testing purposes I'm using a single NFS4 export line (but it fails with any config, that is not relevant): /exports *(ro,fsid=0,no_subtree_check,async) After this point I restarted nfs server, and the mount still failed to produce correct uid/gid values, but then.... So, well, does idmapd run? Yes, I've checked: examachine@cylon:~$ sudo start idmapd start: Job is already running: idmapd Was already running? examachine@cylon:~$ ps aux | grep idmap root 622 0.0 0.0 27336 888 ? Ss 17:35 0:00 rpc.idmapd 1000 2038 0.0 0.0 13128 1060 pts/3 S+ 17:47 0:00 grep --color=auto idmap However, *after* the above command, strangely, idmapd suddenly starts giving the right behavior, could it be a permissions or locking problem or something trivial like that? Or starting idmapd only if nfs I believe I'm using the desktop installation. So, idmapd is running, then what is with the nfs-common config? Oh, well, it does work now, but why didn't it work before? Issuing sudo start idmapd didn't change anything? Ok, the problem might be with the logic that looks at whether nfs4 entries are present on the fstab. I might want to mount them from the command line, etc, and I shouldn't have to start daemons manually to make that happen. Slightly at a loss, although happy that my problem is solved by a Deus Ex Machina :) The point is that, I had to restart idmapd, *even though* the configuration was correct, and the system claimed it to be already running. Those who suffer from this bug, please take note. And please can somebody test this (somewhat unexpected) workaround on a vanilla 11.04 system? Note that I didn't add anything to fstab. That's why it's a little strange. That is to say, there is definitely a bug but I can't pinpoint where exactly. If you need extra information from my system, please let me know. Best Regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662711 Title: idmap should be started by default because mount.nfs now negotiates NFSv4 before NFSv3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/662711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
