I'm seeing some weird behavior with nfs-utils-1.1.3 that doesn't happen with 1.1.2-r1. I share my /usr/portage with NFS. The export is: /usr/portage *(insecure,rw,async,no_root_squash,no_subtree_check) However, when I mount it after upgrading to nfs-utils-1.1.3, I start hitting permissions problems: kirara ~ # touch /usr/portage/foo touch: cannot touch `/usr/portage/foo': Permission denied Everything looks fine with the mount: freyr:/usr/portage on /usr/portage type nfs (rw,user=root,noexec,nosuid,nodev,soft,intr,tcp,addr=192.168.1.84) drwxrwxr-x 160 root root 4096 Aug 21 20:38 /usr/portage Just downgrading nfs-utils to 1.1.2-r1 and remounting makes everything work again.
Here's the reason and solution: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970#40
Have tried all solution proposes http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492970#40 The problem can be solved just adding "sec=sys" to mount options or downgrading nfs-utils to 1.1.2-r1 or older (instead of mentioned, 1.1.4 doesn't work as well). To keep nfs-utils 1.1.3 or newer a linux kernel 2.6.22 or newer may be needed. I can confirm this working out of the box on both gentoo-sources 2.6.23-r3 and 2.6.25-r7.
> To keep nfs-utils 1.1.3 or newer a linux kernel 2.6.22 or newer may be needed. > I can confirm this working out of the box on both gentoo-sources 2.6.23-r3 and > 2.6.25-r7. On the client or server? Because I have 2.6.22-gentoo-r10 on the client and all versions currently in portage (1.1.3, 1.1.4-r1, 1.1.5) show the same error. The workaround with 'sec=sys' works fine at least in 1.1.5 The server runs 2.4.35 with nfs-utils 1.0.6 if IIRC.
Fixed in nfs-utils 1.2.0. Gentoo stable has 1.2.6. Can we close it?