Not both in hex. I meant block# in hex and parent in binary. The only clash this way will be for hard links.
I ran into this while debugging the extra downconvert on dentry locks. Even if I teach the ocfs2 dissector to handle the dentry lock, I won't be able to trim down enough the number of tcpdumps to wade thru (using grep, that is). Block# in hex will help. Mark Fasheh wrote: > On Tue, Apr 15, 2008 at 06:54:27PM -0700, Sunil Mushran wrote: > >> Any reason the dentry lock has parent# in string and block# in binary? >> > > Afair, there were space constraints to printing them both in hex. > --Mark > > -- > Mark Fasheh > _______________________________________________ Ocfs2-devel mailing list Ocfs2-devel@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-devel
