On May. 19, 2008, 11:14 +0300, xing jing <xingjing@xxxxxxxxxx> wrote: > hi,all > 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. > > best regards！ > > Jing > > > PS, there is some file handles from the trace > > bcdaa400ce7a23012000000000a4dabcce7a230164860000a0cf90002e303000 > b7905500246c6a1220000000000cec5413b72e3264860000a0cf90002e303000 > bcdaa400ce7a23012000000000a4dabcce7a230164860000a0cf90002e303000 > bcdaa400ce7a230120000000004ad8e8f8b2230164860000a0cf90002e303000 > bcdaa400ce7a230120000000004ad8e8f8b2230164860000a0cf90002e303000 > bcdaa400ce7a230120000000001074cd975e480564860000a0cf90002e303000 What server generated them? This doesn't look like the linux nfsd format (as defined in include/linux/nfsd/nfsfh.h) That file handle contents are opaque to the client so you'd need to have the server's code or reverse engineer its structure. Try running ls -li on a file and parent directory and see if you can identify the respective inode numbers in the filehandle. (likely to be coded in big-endian) Benny > -- > 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
