OT - NFS group ignored [SOLVED]

[James A. Peltier]

----- Original Message -----
| On 07/25/2015 08:31 PM, Cameron Simpson wrote:
| > On 26Jul2015 10:39, Ed Greshko <ed.greshko at greshko.com> wrote:
| >> On 07/26/15 10:34, Cameron Simpson wrote:
| >>> On 26Jul2015 08:06, Ed Greshko <ed.greshko at 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 <cs at 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

Have a look at /etc/sysconfig/nfs for adding persistence to your options. ;)

-- 
James A. Peltier
IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 604-365-6432
Fax     : 778-782-3045
E-Mail  : jpeltier at sfu.ca
Website : http://www.sfu.ca/itservices
Twitter : @sfu_rcg
Powering Engagement Through Technology