From: NeilBrown <neilb@suse.de>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: NFS <linux-nfs@vger.kernel.org>
Subject: What is the long term fix for the idmapper key-quota problem.
Date: Mon, 21 Oct 2013 16:05:14 +1100 [thread overview]
Message-ID: <20131021160514.4dbcbf12@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
Hi,
as you probably know, request_key() imposes a quota on
the number of keys that can be requested, which by default is quite low (200).
When idmap exceeds this quota, request_key() returns an error and
the result is userspace sees "nobody" as the owner.
A short term fix is to fiddle some sysctl values, but I wonder if any long
term fix is being planned.
Probably the sensible thing would be for nfs-idmap to bypass the quota.
As keys are not held active for very long at a time, they should be garbage
collected in due course.
There is currently no interface to request this but I suspect one could be
added.
(I want to fixed this for openSUSE-13.1, and don't want to diverge too far
from mainline).
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2013-10-21 5:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 5:05 NeilBrown [this message]
2013-10-22 14:49 ` What is the long term fix for the idmapper key-quota problem Anna Schumaker
2013-10-22 21:30 ` NeilBrown
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=20131021160514.4dbcbf12@notabene.brown \
--to=neilb@suse.de \
--cc=bjschuma@netapp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.