From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: David Flynn <davidf@rd.bbc.co.uk>
Cc: linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: NFS4 BAD_STATEID loop (kernel 3.0.4)
Date: Mon, 24 Oct 2011 17:31:42 +0200 [thread overview]
Message-ID: <1319470302.2734.4.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20111024145027.GF32587@rd.bbc.co.uk>
On Mon, 2011-10-24 at 14:50 +0000, David Flynn wrote:
> No. Time Source Destination Protocol Size Info
> 39 15:33:59.077143 172.29.190.28 172.29.120.140 NFS 370 V4 COMPOUND Call (Reply In 40) <EMPTY> PUTFH;WRITE;GETATTR
>
> Frame 39: 370 bytes on wire (2960 bits), 370 bytes captured (2960 bits)
> Ethernet II, Src: ChelsioC_07:49:6f (00:07:43:07:49:6f), Dst: All-HSRP-routers_be (00:00:0c:07:ac:be)
> Internet Protocol, Src: 172.29.190.28 (172.29.190.28), Dst: 172.29.120.140 (172.29.120.140)
> Transmission Control Protocol, Src Port: omginitialrefs (900), Dst Port: nfs (2049), Seq: 40433, Ack: 7449, Len: 304
> Remote Procedure Call, Type:Call XID:0x43ce4e16
> Network File System
> [Program Version: 4]
> [V4 Procedure: COMPOUND (1)]
> Tag: <EMPTY>
> length: 0
> contents: <EMPTY>
> minorversion: 0
> Operations (count: 3)
> Opcode: PUTFH (22)
> filehandle
> length: 36
> [hash (CRC-32): 0x6e4b15f3]
> decode type as: unknown
> filehandle: 7df3a75d5e1cd908000ab44c5b000000efc80200000a0300...
> Opcode: WRITE (38)
> stateid
Do you have an example of the stateid argument's value? Does it change
at all between separate WRITE attempts?
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-10-24 15:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 10:40 NFS4 BAD_STATEID loop (kernel 3.0) David Flynn
2011-10-24 11:22 ` Trond Myklebust
2011-10-24 13:17 ` David Flynn
2011-10-24 13:32 ` Trond Myklebust
2011-10-24 14:50 ` NFS4 BAD_STATEID loop (kernel 3.0.4) David Flynn
2011-10-24 15:31 ` Trond Myklebust [this message]
2011-10-24 15:55 ` David Flynn
2011-10-27 22:17 ` David Flynn
2011-10-29 0:25 ` NFS4ERR_STALE_CLIENTID loop David Flynn
2011-10-29 17:29 ` Trond Myklebust
2011-10-29 18:02 ` David Flynn
2011-10-29 18:22 ` Myklebust, Trond
2011-10-29 18:23 ` Chuck Lever
2011-10-29 18:26 ` Myklebust, Trond
2011-10-29 18:29 ` David Flynn
2011-10-29 18:15 ` J. Bruce Fields
2011-10-29 18:21 ` Myklebust, Trond
2011-10-29 18:47 ` J. Bruce Fields
2011-10-29 18:50 ` Chuck Lever
2011-10-29 19:19 ` Myklebust, Trond
2011-10-29 19:52 ` David Flynn
2011-10-29 20:42 ` Myklebust, Trond
2011-10-29 21:07 ` David Flynn
2011-10-29 21:12 ` Myklebust, Trond
2011-10-31 13:07 ` Chuck Lever
2011-10-31 13:21 ` David Flynn
2011-10-31 13:39 ` Chuck Lever
2011-10-24 13:43 ` NFS4 BAD_STATEID loop (kernel 3.0) Chuck Lever
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=1319470302.2734.4.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=davidf@rd.bbc.co.uk \
--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).