Return-Path: Received: from plane.gmane.org ([80.91.229.3]:46526 "EHLO plane.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbcAIEzK (ORCPT ); Fri, 8 Jan 2016 23:55:10 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aHlYR-0004WU-1H for linux-nfs@vger.kernel.org; Sat, 09 Jan 2016 05:55:07 +0100 Received: from cpe-72-128-83-163.wi.res.rr.com ([72.128.83.163]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Jan 2016 05:55:07 +0100 Received: from rbarr138 by cpe-72-128-83-163.wi.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 09 Jan 2016 05:55:07 +0100 To: linux-nfs@vger.kernel.org From: Robb Barrows Subject: Re: NFS v4, are special steps required for uid/gid to work, even if they are the same on server and client? Date: Fri, 8 Jan 2016 22:52:12 +0000 (UTC) Message-ID: References: <20160108202357.GE5031@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-nfs-owner@vger.kernel.org List-ID: J. Bruce Fields 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