Linux NFS development
 help / color / mirror / Atom feed
From: Robb Barrows <rbarr138@gmail.com>
To: linux-nfs@vger.kernel.org
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)	[thread overview]
Message-ID: <loom.20160108T220444-687@post.gmane.org> (raw)
In-Reply-To: 20160108202357.GE5031@fieldses.org

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






  reply	other threads:[~2016-01-09  4:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 23:02 NFS v4, are special steps required for uid/gid to work, even if they are the same on server and client? Robb
2016-01-08 20:23 ` J. Bruce Fields
2016-01-08 22:52   ` Robb Barrows [this message]
2016-01-11 18:47     ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20160108T220444-687@post.gmane.org \
    --to=rbarr138@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox