From: Jeff Layton <jlayton@redhat.com>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS4ERR_DELAY (was: NFS4: ssh + unlink(~/.Xauthority) delays)
Date: Tue, 21 Aug 2012 06:41:00 -0400 [thread overview]
Message-ID: <20120821064100.701ec6e9@corrin.poochiereds.net> (raw)
In-Reply-To: <k0vjq7$o7l$1@ultimate100.geggus.net>
On Tue, 21 Aug 2012 09:19:03 +0000 (UTC)
Sven Geggus <lists@fuchsschwanzdomain.de> wrote:
> Sven Geggus <lists@fuchsschwanzdomain.de> wrote:
>
> > So the question is what cases hangs in NFS4 based Linux systems in general
> > an in this particular case?
>
> Digging this down a little bit further using wireshark I figured out that
> the server responds to the REMOVE .Xauthority call with an NFS4ERR_DELAY for
> whatever reason.
>
> This is a currently a test-machine with one single user and next to zero
> load.
>
> So I will probably need a hint on how to debug the server behaviour, as a
> NFS4ERR_DELAY response is definitely not expected in this case.
>
> Sven
>
It's often the case that this indicates a problem communicating over
the callback channel. For instance, the server is trying to recall a
delegation but the client isn't responding, so the server has to wait
until the recall attempt times out before proceeding.
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-08-21 10:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 8:25 NFS4: ssh + unlink(~/.Xauthority) delays Sven Geggus
2012-08-21 9:19 ` NFS4ERR_DELAY (was: NFS4: ssh + unlink(~/.Xauthority) delays) Sven Geggus
2012-08-21 10:41 ` Jeff Layton [this message]
2012-08-21 12:52 ` NFS4ERR_DELAY Sven Geggus
2012-08-21 13:07 ` NFS4ERR_DELAY Jeff Layton
2012-08-21 17:47 ` NFS4ERR_DELAY J. Bruce Fields
2012-08-22 8:33 ` NFS4ERR_DELAY Sven Geggus
2012-08-21 12:59 ` NFS4: ssh + unlink(~/.Xauthority) delays Jim Rees
2012-08-21 16:04 ` Sven Geggus
2012-08-21 17:07 ` Jim Rees
2012-08-21 18:03 ` Malahal Naineni
2012-08-21 18:42 ` Jim Rees
2012-08-21 20:59 ` J. Bruce Fields
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=20120821064100.701ec6e9@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lists@fuchsschwanzdomain.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 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.