Linux NFS development
 help / color / mirror / Atom feed
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: xing jing <xingjing-3pZTqkFmMFknDS1+zs4M5A@public.gmane.org>,
	Benny Halevy <bhalevy@panasas.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: how to parse the 64byte NFSv3 file handle
Date: Mon, 19 May 2008 07:08:38 -0400	[thread overview]
Message-ID: <RTPCLUEXC1-PRDpAOAk000000fd@RTPMVEXC1-PRD.hq.netapp.com> (raw)
In-Reply-To: <483140C4.3010104@panasas.com>

At 04:56 AM 5/19/2008, Benny Halevy wrote:
>On May. 19, 2008, 11:14 +0300, xing jing <xingjing-3pZTqkFmMFknDS1+zs4M5A@public.gmane.org> wrote:
>> recently, I want to get some information (like file access patten)
>> from a trace of NFS client. The simplest way may be parse the file
>> handle to get the file ino and directory ino, but I don't know how to
>> get them from the 64 of 16 hexadecimal. Can you tell me how to parse
>> file handle to get useful information, thanks very much.
>
>That file handle contents are opaque to the client so you'd
>need to have the server's code or reverse engineer its
>structure.

Wireshark understands the format of many NFS server filehandles. You
can simply zoom-in on the filehandle in the details pane to see much of
this. Alternatively, you can look back in the trace to find the LOOKUP
or READDIR/READDIRPLUS to find the mapping between name and
filehandle.

By the way, not all filehandles are 64 bytes. That, too, is a server-specific
choice.

Tom.


  reply	other threads:[~2008-05-19 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  8:14 how to parse the 64byte NFSv3 file handle xing jing
     [not found] ` <483136FC.4050208-3pZTqkFmMFknDS1+zs4M5A@public.gmane.org>
2008-05-19  8:56   ` Benny Halevy
2008-05-19 11:08     ` Talpey, Thomas [this message]
     [not found]       ` <RTPCLUEXC1-PRDpAOAk000000fd-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-05-19 14:28         ` Trond Myklebust
2008-05-19 14:36         ` Chuck Lever
2008-05-19 14:44           ` Talpey, Thomas

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=RTPCLUEXC1-PRDpAOAk000000fd@RTPMVEXC1-PRD.hq.netapp.com \
    --to=thomas.talpey@netapp.com \
    --cc=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xingjing-3pZTqkFmMFknDS1+zs4M5A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox