On 07/25/2015 08:31 PM, Cameron Simpson wrote: > On 26Jul2015 10:39, Ed Greshko <ed.gres...@greshko.com> wrote: >> On 07/26/15 10:34, Cameron Simpson wrote: >>> On 26Jul2015 08:06, Ed Greshko <ed.gres...@greshko.com> wrote: >>>> But, FWIW, I'm trying to replicate a failure here and can't. >>> >>> My standard question in this situation is: how many groups is the user in >>> on the client machine? >>> >> Well, in my non-failing case, just 2. >> >> Not heard of a limitation in that area. > > Historically there was a 16 group protocol limit on what the client passed to > the NFS server, so unless the file's group was in your first 15 secondary > groups it would not be consulted for file access. > > Let's see what the OP has to deal with. > > Cheers, > Cameron Simpson <c...@zip.com.au>
Turns out this is the clue I needed. Using the search "NFS4 group ID limitations", I found this article: http://www.xkyle.com/solving-the-nfs-16-group-limit-problem/ Running rpc.mountd --manage-gids on the server seems to have fixed my problem. I don't know if that command is persistent, but I will soon :-) Thanks for all your suggestions. Emmett -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
