Comment 6 for bug 480444

I looked at the packet storm (captured above), and it seems to be a rapid repetition of a single
command and a single response.
The command is a COMPOUND of PUTFH, WRITE, GETATTR,
and the server responds with NFS4ERR_OPENMODE which is
in response to a failure of the WRITE.

Now, it is odd that there is a WRITE command as part of a ftruncate() syscall.
The WRITE carries 1024 bytest of data each time.
The offset (place where it is supposed to be written) is always fairly small, but different each time.

There seem to be bursts of many of the COMPOUNDS sometimes.

My packet storm is attached (wireshark .pcap file), and not quite the same, but similar.

I get COMPOUND call <EMPTY tag> PUTFH; LOCK
... PUTFH; WRITE; GETATTR
... RENEW
... PUTFH; LOCK
         (tries to set a WRITE_LT lock)
... PUTF; WRITE; GETATTR
         The write is always 543 bytes;
          The getattr asks for FATTR4_CHANGE and FATTR4_SIZE
                            and FATTR4_TIME_METADATA and FATTR4_TIME_MODIFY
... RENEW
... PUTFH; LOCK
... PUTFH; WRITE; GETATTR
... RENEW
et cetera
The "renew" calls succeed with NFS4_OK
PUTFH; LOCK succeeds with NFS4_OK (twice).
PUTFH; WRITE; GETATTR fails on the WRITE with NFS4ERR_OPENMODE