From: NeilBrown <neilb@suse.de>
To: Rik Theys <Rik.Theys@esat.kuleuven.be>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS server caches client mount permissions?
Date: Wed, 2 Jul 2014 12:20:43 +1000 [thread overview]
Message-ID: <20140702122043.1c1c2c2d@notabene.brown> (raw)
In-Reply-To: <53B2B1AD.4080507@esat.kuleuven.be>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Tue, 01 Jul 2014 15:03:41 +0200 Rik Theys <Rik.Theys@esat.kuleuven.be>
wrote:
> Hi,
>
> We use NFS4 to export data to other clients. The exports file has the
> directories exported to netgroups, for example:
>
> /export @nfs(rw,async,no_subtree_check,fsid=0)
> /export/data1 @nfs(rw,async,no_subtree_check)
> /export/data2 @nfs(rw,async,no_subtree_check)
>
> If we forget to add a new client to the netgroup, the server rejects the
> mount from the client (as it should). But when we then add the client to
> the netgroup it can take up to 15 minutes for the server to accept the
> new client.
>
> Using 'getent netgroup nfs' on the server immediately shows the new
> entry of the client.
>
> Running exportfs -rv to reload the exports also doesn't help.
>
> Does nfsd cache mount access (rejections) somewhere? How can I
> flush/tune this cache? Preferably without restarting the NFS server as
> that causes a 90s interruption due to the grace period.
Does
exportfs -f
help? It flushes the cache (which is normally updated ever 15 minutes).
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-07-02 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 13:03 NFS server caches client mount permissions? Rik Theys
2014-07-02 2:20 ` NeilBrown [this message]
2014-07-02 6:58 ` Rik Theys
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=20140702122043.1c1c2c2d@notabene.brown \
--to=neilb@suse.de \
--cc=Rik.Theys@esat.kuleuven.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox