From: Bruce Guenter <bruce@untroubled.org>
To: linux-nfs@vger.kernel.org
Subject: Looping NFSv4 traffic
Date: Mon, 13 May 2013 14:22:20 -0600 [thread overview]
Message-ID: <20130513202220.GA16969@untroubled.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
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've put a tcpdump recording up here:
http://untroubled.org/nfsv4.tcpdump.xz
This behavior seems to be most reliably triggered by using Chromium, but
I have observed it continuing even after shutting that down. I am able
to continue to use the client while this behavior is going on, albeit
with considerably reduced NFS performance.
What is going on here?
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-05-13 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:22 Bruce Guenter [this message]
2013-06-19 21:57 ` Looping NFSv4 traffic Bruce Guenter
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=20130513202220.GA16969@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).