All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bian Naimeng <biannm@cn.fujitsu.com>
To: "Tayade, Nilesh" <Nilesh.Tayade@netscout.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Query regarding NFS packet capture at application layer - umount operation.
Date: Tue, 07 Sep 2010 15:47:48 +0800	[thread overview]
Message-ID: <4C85EE24.9070007@cn.fujitsu.com> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B90D19835A@nsmail.netscout.com>

> Hi,
> 
> I have a query related to NFS packet captured at application layer. I
> have setup the NFS node on local system itself (just for test purpose). 
> And capturing the packets for various events (mount, umount, file access
> etc) on loop-back interface itself. However, in case of the umount
> scenario, I do not see any NFS packet captured (I can only see three TCP
> packets exchanged). 
> 
> Could someone please explain why there is no NFS packet observed during
> an unmount? Also there seems not much information, related to NFS mount
> point being unmounted, in TCP packet. So is there any way to detect the
> unmount operation by hacking such packets?
> 

  I guess you used NFSv4. NFSv4 umount operation does not send any NFS packet.
  The TCP packets you captured were sent by TCP close procedure, because NFS
  umount operation need close the TCP connection with NFS server.

-- 
Regards
Bian Naimeng


  reply	other threads:[~2010-09-07  7:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 12:33 Query regarding NFS packet capture at application layer - umount operation Tayade, Nilesh
2010-09-07  7:47 ` Bian Naimeng [this message]
2010-09-07  8:02   ` Tayade, Nilesh
2010-09-07 17:19     ` Jeff Layton
2010-09-07 17:31       ` J. Bruce Fields
2010-09-08  5:34         ` Tayade, Nilesh
  -- strict thread matches above, loose matches on Subject: below --
2010-09-07  6:19 Tayade, Nilesh

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=4C85EE24.9070007@cn.fujitsu.com \
    --to=biannm@cn.fujitsu.com \
    --cc=Nilesh.Tayade@netscout.com \
    --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 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.