From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: linux-image: on nfs4 server: RPC: AUTH_GSS upcall timed out Please check user daemon is running
Date: Fri, 09 Dec 2011 13:31:08 -0500 [thread overview]
Message-ID: <4EE253EC.2040609@fifthhorseman.net> (raw)
In-Reply-To: <20111208174501.GA30088@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On 12/08/2011 12:45 PM, J. Bruce Fields wrote:
> Yes, if you're using NFSv4 then the client and server should each run
> both daemons.
ah, thanks.
>> If so, what functionality am i losing out on by not running it?
>
> You lose NFSv4.0 delegations, which depend on the ability for the server
> to contact the client to send delegation recalls. Delegations are
> optional, so you won't lose correctness, but you may lose some
> performance.
Thanks, that's useful. Do the clients need to run cachefilesd as well
to take advantage of delegation? Is there a document where i could find
this sort of information without adding noise to the list?
> If you're using only v2, v3, or v4.1, that doesn't matter. (v2 and v3
> lack delegations, and v4.1 sends callbacks over existing
> client-established connections).
OK, gotcha. Is it possible to use 4.1 with linux kernel 3.1 and
nfs-utils 1.2.5, or would i need to pull a more recent version?
Thanks, and sorry for the basic questions,
--dkg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]
next prev parent reply other threads:[~2011-12-09 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 15:29 linux-image: on nfs4 server: RPC: AUTH_GSS upcall timed out Please check user daemon is running Daniel Kahn Gillmor
2011-12-08 17:45 ` J. Bruce Fields
2011-12-09 18:31 ` Daniel Kahn Gillmor [this message]
2011-12-09 19:10 ` J. Bruce Fields
2012-02-23 5:58 ` Daniel Kahn Gillmor
2012-02-28 19:49 ` J. Bruce Fields
2013-08-11 13:15 ` Mario Bachmann
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=4EE253EC.2040609@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=bfields@fieldses.org \
--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.