Public bug reported: Hardy and possibly Intrepid are affected by a bug in rpc.mountd's --manage-gids option.
This was fixed upstream somewhere between nfs-utils version 1.1.3 and 1.1.4. The problem is that mountd in nfs-utils <= 1.1.2 returns a negative response if there are no GIDs found for the UID on the server. The patch to rpc.mountd is trivial and makes it return a zero-length list which the kernel will handle correctly. Even though --manage-gids isn't switched on by default until Jaunty this bug should really be fixed as it completely breaks NFS-operation and there is really no logmessage indicating what is going on. The --manage-gids option is advertised in manpages. The patch to this problem was committed to the nfs-utils git repository in commit 86c3a79a108091fe08869a887438cc2d4e1126ed My thread on linux-nfs about this issue shows my difficulties tracing the problem: http://marc.info/?t=125847253800001&r=1&w=2 J. Bruce Fields helped track it down to the commit above in this message: http://marc.info/?l=linux-nfs&m=125934869022070&w=2 Attached is said commit to the git-repository as shown in Bruce's reply. ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: hardy intrepid -- An issue with rpc.mountd's --manage-gids option makes NFS operations hang https://bugs.launchpad.net/bugs/489499 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
