All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Pavel Karneliuk <pavel.karneliuk@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: Reliable NFS statistics tool to monitoring all incoming network traffic
Date: Thu, 20 Feb 2014 12:55:23 -0500	[thread overview]
Message-ID: <5306418B.9060007@RedHat.com> (raw)
In-Reply-To: <CA+NKcRwjoaeQUZEGSeVC+Tfa3jDzvTLt1RBjSQrkj6KJMcC-zg@mail.gmail.com>



On 02/20/2014 10:39 AM, Pavel Karneliuk wrote:
> Hello linux-nfs members,
> 
> I am looking for some tool for monitoring all incoming traffic on the
> wire and collecting NFSv3 operations over TCP transport protocol in
> 1G-10G networks.
> 
> Could you advise me some fast and reliable utility?
> 
> I have tried NFSwatch tool, but its results are not reliable.
> At first, I mount NFSv3 directory with TCP transport protocol and wsize=512k
> 
> sudo mount -v -t nfs 10.6.136.187:/share /mnt/nfs-fedora/ -o
> rw,vers=3.0,tcp,wsize=524288
> 
> then I write 10Mb file to NFS server:
> 
> sudo dd if=/dev/zero of=/mnt/nfs-fedora/zero.data bs=1M count=10
> 
> I expect to see 20 WRITE operations (10Mb / 512Kb == 20).
> The nfsstat (nfsstat --nfs -3 -Z) shows exactly 20 WRITE operations,
> because it takes statistic from the kernel.
> 
> When I try to get the same result with NFSwatch by (sudo nfswatch -all
> -procs3 -t 20)
> I get unreproducible results with 1 or 2 registered WRITE operations.
> NFSwatch works well on NFSv3 over UDP, but loses almost all READ/WRITE
> operations in case of TCP protocol.
> I have checked its source code and found that NFSwatch doesn't
> performs reassembling TCP streams between NFS server and NFS client.
> It just looks at TCP segment and expects headers of RPC/NFSv3
> operations exactly after TCP header.
> 
> The tcpdump works similarly. Wireshark(and Tshark) is too slow for
> live 1G-10G NFSv3/TCP traffic capturing and filtration.
> 
> 
> Would you suggest some alternative utils, solutions or workarounds?
You can try mountstats(8) or nfsiostat(8). Both of them 
manipulate data collected in /proc/self/mountstats 

steved.


  reply	other threads:[~2014-02-20 17:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 15:39 Reliable NFS statistics tool to monitoring all incoming network traffic Pavel Karneliuk
2014-02-20 17:55 ` Steve Dickson [this message]
2014-02-21  9:53   ` Pavel Karneliuk
2014-02-21 13:23     ` Weston Andros Adamson
2014-02-21 14:40     ` 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=5306418B.9060007@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=pavel.karneliuk@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.