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@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
