From: Bruce Guenter <bruce@untroubled.org>
To: linux-nfs@vger.kernel.org
Subject: Re: Looping NFSv4 traffic
Date: Wed, 19 Jun 2013 15:57:04 -0600 [thread overview]
Message-ID: <20130619215704.GA32209@untroubled.org> (raw)
In-Reply-To: <20130513202220.GA16969@untroubled.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On Mon, May 13, 2013 at 02:22:20PM -0600, Bruce Guenter wrote:
> I'm seeing repeated duplicated queries going on between a NFSv4 client
> and server. Both client and server are running linux v3.9.2, but I have
> observed this with other versions on both.
>
> Wireshark decodes it as (copied by hand):
>
> V4 Call (Reply In 3) WRITE StateID:0x1c7c Offset:0 Len:8192
> V4 Reply (Call In 2) WRITE Status: NFS4ERR_OLD_STATEID
I am still seeing this behavior with the client running v3.10-rc6 and
server on v3.9.3. The last two times I've seen it, gvfsd-metadata has
been blocked in D state.
Does anybody have any idea what's going on here?
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-06-19 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:22 Looping NFSv4 traffic Bruce Guenter
2013-06-19 21:57 ` Bruce Guenter [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=20130619215704.GA32209@untroubled.org \
--to=bruce@untroubled.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.