On Thu, 2012-05-31 at 17:24 +0400, Michael Tokarev wrote: > On 31.05.2012 16:59, Myklebust, Trond wrote: > [] > > That is tcpdump trying to interpret your NFSv4 trace as NFSv2/v3. > > Oh. > > > Can you either please use wireshark to provide a full text dump (using > > something like 'tshark -V -O nfs,rpc'), or just send us the binary > > tcpdump output using 'tcpdump -w /tmp/foo -s 90000'? > > I started tcpdump: > > tcpdump -npvi br0 -s 0 host 192.168.88.4 and \( proto ICMP or port 2049 \) -w nfsdump > > on the client (192.168.88.2). Next I mounted a directory on the client, > and started reading (tar'ing) a directory into /dev/null. It captured a > few stalls. Tcpdump shows number of packets it got, the stalls are at > packet counts 58090, 97069 and 97071. I cancelled the capture after that. > > The resulting file is available at http://www.corpit.ru/mjt/tmp/nfsdump.xz , > it is 220Mb uncompressed and 1.3Mb compressed. The source files are > 10 files of 1Gb each, all made by using `truncate' utility, so does not > take place on disk at all. This also makes it obvious that the issue > does not depend on the speed of disk on the server (since in this case, > the server disk isn't even in use). OK. So from the above file it looks as if the traffic is mainly READ requests. In 2 places the server stops responding. In both cases, the client seems to be sending a single TCP frame containing several COMPOUNDS containing READ requests (which should be legal) just prior to the hang. When the server doesn't respond, the client pings it with a RENEW, before it ends up severing the TCP connection and then retransmitting. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com ��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
