libglusterfsclient: Call inode_lookup to prevent pruning

This bug shows up while using unfs3 with replicate. The absence
of an inode_lookup on a looked-up/created inode results in it
getting pruned from the inode table. Consequently, a subsequent
lookup for the inode results in a different inode number being
returned by replicate. This breaks unfs3 because it tries to remember
the inode numbers returned by two different stat-family calls.

Resolves: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=11

Signed-off-by: Anand V. Avati <avati@dev.gluster.com>

0 files changed, 0 insertions, 0 deletions