From: "Talpey, Thomas" Subject: Re: how to parse the 64byte NFSv3 file handle Date: Mon, 19 May 2008 10:44:31 -0400 Message-ID: References: <483136FC.4050208@ncic.ac.cn> <483140C4.3010104@panasas.com> <8762271D-9645-49DF-B218-E626F704DC96@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: xing jing , Benny Halevy , Linux NFS Mailing List To: Chuck Lever Return-path: Received: from mx2.netapp.com ([216.240.18.37]:21202 "EHLO mx2.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758122AbYESOof (ORCPT ); Mon, 19 May 2008 10:44:35 -0400 In-Reply-To: <8762271D-9645-49DF-B218-E626F704DC96@oracle.com> References: <483136FC.4050208-3pZTqkFmMFknDS1+zs4M5A@public.gmane.org> <483140C4.3010104@panasas.com> <8762271D-9645-49DF-B218-E626F704DC96@oracle.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: At 10:36 AM 5/19/2008, Chuck Lever wrote: >Also, there is a checkbox in the NFS decoder preference pane for >enabling wireshark to associated file handles with file names and >display the file names where appropriate. >The checkbox is "Snoop FH to filename mappings". Ooh- didn't know about that one. Cool. It can even build the entire directory <-> FH tree to show the full pathname, if available. http://wiki.wireshark.org/NFS_Preferences Tom.