J. Bruce Fields <bfields@...> writes: > > So my real question is why cant user:user create a file in /test/chmod775 ? > > Hm, and chmod775 should permit write to members of common, and user is a > member of common on both client and server (and names and uids are the > same on both). > > I'm not seeing the explanation.... > > I think the next thing I'd do would be get a network trace: > > 1. run "tcpdump -s0 -wtmp.pcap" > 2. try the failed "touch /test/chmod755/file" > 3. kill the tcpdump > > Then run "wireshark tmp.pcap" and look at the result. If this is v4 > thee should be an OPEN call in there that tries to create "file", with > the server replying with an error. > > It'd be especially interesting to look at the rpc header on that call, > specifically the credential, which should include a list of gid's (with > 20000 being one of those gid's). > I did this and indeed 20000 was not in the list of "Auxiliary GIDs" of the rpc header credentials as it should of been. A reboot fixed this, so now it works. I had restarted the terminal but it looks since I had other sessions logged in that wasn't enough to get the new gid to propogate, I should know better. Running # sudo newgrp common Probably would of fixed it for me, as it adds you to the group without requiring logging out, I'll never trust the "groups" command again :) Thank you helping me find the issue. -Robb -- 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
