From: Frank van Maarseveen <frankvm@frankvm.com>
To: Stephan Henningsen <sth@amplex.dk>
Cc: nfs@lists.sourceforge.net
Subject: Re: Trouble accessing NFS mountpoint as user
Date: Thu, 4 Jan 2007 22:00:41 +0100 [thread overview]
Message-ID: <20070104210041.GA15676@janus> (raw)
In-Reply-To: <459CD54E.9050107@amplex.dk>
On Thu, Jan 04, 2007 at 11:22:06AM +0100, Stephan Henningsen wrote:
> Trond Myklebust wrote:
> > NFS will only support a maximum of 16 supplemental groups. That is a
> > protocol limitation, not a Linux implementation issue.
>
> I just did "chgrp dialout /var/files" on the server, changing to one of the
> first 16 supplemental groups, and now it works. Thank you very much for
> solving this mystery!
>
> > See for instance
> > http://nfsworld.blogspot.com/2005/03/whats-deal-on-16-group-id-limitation.html
> > if you want a more complete explanation of why this is the case.
>
> This suggests moving from NFS3 to NFS4. Is that an easy task? Mount as
> "nfs4" instead of "nfs" and compile the kernel nfs server to support nfs4?
There's an alternative: See http://www.frankvm.com/nfs-ngroups/ for a
patch to get rid of the 16 groups limit on linux NFS2/NFS3 clients without
breaking the protocol.
--
Frank
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 8:23 Trouble accessing NFS mountpoint as user Stephan Henningsen
2007-01-04 9:09 ` Trond Myklebust
2007-01-04 10:22 ` Stephan Henningsen
2007-01-04 21:00 ` Frank van Maarseveen [this message]
2007-01-05 6:56 ` Stephan Henningsen
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=20070104210041.GA15676@janus \
--to=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
--cc=sth@amplex.dk \
/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