On Wed, Sep 15, 2010 at 02:35:43AM -0400, Tayade, Nilesh wrote: > > -----Original Message----- > > From: Chuck Lever [mailto:chuck.lever@xxxxxxxxxx] > > Sent: Tuesday, September 14, 2010 8:50 PM > > To: Tayade, Nilesh > > Cc: linux-nfs@xxxxxxxxxxxxxxx > > Subject: Re: NFS : filehandle to filename mappings. > > > > > > On Sep 14, 2010, at 8:10 AM, Tayade, Nilesh wrote: > > > > > > > > > Could someone please provide some information on how it gets the > > file > > > name in some of the packets (i.e. related to LOOKUP, WRITE etc.)? > > Does > > > it refer the lookup table at NFS server side and fills-in the name > > in > > > response? > > > > Some NFS operations include a filename. LOOKUP includes a filename > > because it is the premier way to convert a filename + directory to a > > file handle. By and large, though, the NFS protocol deals in file > > handles, so that's what you will see in most NFS wire operations. > > > > If you want to see the filename associated with a file handle, > > you'll need to manage a table of mappings based on what has gone by > > on the wire. This is, for example, what wireshark does for it's NFS > > protocol display. NFS clients cache this information as well. > > Thanks for the response. So filename-filehandle mapping extraction seems > implementation dependent. Keep in mind also that unlink, link, and rename mean that the mapping is many-to-one and changes over time. --b. > > > > > I recommend Brent Callaghan's seminal reference "NFS Illustrated" > > for a full overview of NFS operation. > > > > > > http://www.pearsonhighered.com/educator/academic/product/0,,02013257 > > 05,00%2Ben-USS_01DBC.html?type=ABI > > Thanks. I shall take a look. > > > > > -- > > Chuck Lever > > chuck[dot]lever[at]oracle[dot]com > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
