From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andi Kleen <ak@suse.de>
Cc: Robert Szentmihalyi <robert.szentmihalyi@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: Group limit for NFS exported file systems
Date: Wed, 23 Aug 2006 10:13:57 -0400 [thread overview]
Message-ID: <1156342438.10481.39.camel@localhost> (raw)
In-Reply-To: <p73u043656n.fsf@verdi.suse.de>
On Wed, 2006-08-23 at 13:51 +0200, Andi Kleen wrote:
> "Robert Szentmihalyi" <robert.szentmihalyi@gmx.de> writes:
>
> > is there a group limit for NFS exported file systems in recent kernels?
> > One if my users cannot access directories that belong to a group he actually _is_ a member of. That, however, is true only when accessing them over NFS. On the local file system, everything is fine. UIDs and GIDs are the same on client and server, so that cannot be the problem. Client and server run Gentoo Linux with kernel 2.6.16 on the server and 2.6.17 on the client.
>
> NFSv2 has a 8 groups limit in the protocol iirc.
16, and it is a limitation of the RPC protocol's AUTH_UNIX/AUTH_SYS
authentication scheme, rather than being specific to NFS.
Note that if you use KerberosV based authentication at your workplace,
then you can migrate your NFS setup to the stronger RPCSEC_GSS/krb5
authentication. That also happens to fix the 16 groups limit problem.
Cheers,
Trond
next prev parent reply other threads:[~2006-08-23 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 9:16 Group limit for NFS exported file systems Robert Szentmihalyi
2006-08-23 9:32 ` Jan Engelhardt
2006-08-23 9:43 ` Robert Szentmihalyi
2006-08-23 10:55 ` Ray Lee
2006-08-23 11:11 ` Robert Szentmihalyi
2006-08-23 11:35 ` Ray Lee
2006-08-23 11:57 ` Jan Engelhardt
2006-08-23 13:01 ` Ray Lee
2006-08-23 14:20 ` Peter Staubach
2006-08-23 11:51 ` Andi Kleen
2006-08-23 14:13 ` Trond Myklebust [this message]
2006-08-23 15:36 ` Peter Staubach
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=1156342438.10481.39.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.szentmihalyi@gmx.de \
/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