From: "J. Bruce Fields" <bfields@fieldses.org>
To: philippe.deniel@cea.fr
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS4ERR_DELAY and OP4_PUTROOTFH
Date: Sat, 26 Jun 2010 11:15:02 -0400 [thread overview]
Message-ID: <20100626151502.GA3432@fieldses.org> (raw)
In-Reply-To: <4C246006.10708@cea.fr>
On Fri, Jun 25, 2010 at 09:51:34AM +0200, philippe.deniel@cea.fr wrote:
> Hi,
>
> in which situation would OP4_PUTROOTFH return NFS4ERR_DELAY ? I have
> seen in rfc5661 that PUTROOTFH can return such an error, but I can't
> figure out when this can occur.
That depends entirely on the server implementation. In the case of the
Linux server, it depends on an upcall to a userland daemon to find the
root, and the userland daemon may be slow or unresponsive.
--b.
prev parent reply other threads:[~2010-06-26 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 7:51 NFS4ERR_DELAY and OP4_PUTROOTFH philippe.deniel
2010-06-26 15:15 ` J. Bruce Fields [this message]
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=20100626151502.GA3432@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=philippe.deniel@cea.fr \
/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