gluster3.3 cFuse client dying after "gfid different on subvolume" ?

[Mingfan Lu <mingfan.lu@xxxxxxxxx>]

Hi

   I saw one of our client dying after we see "gfid different on subvolume". Here is log of the client

[2014-03-03 08:30:54.286225] W [afr-common.c:1196:afr_detect_self_heal_by_iatt] 0-bj-mams-replicate-6: /operation/video/2014/03/03/e7/35/71/81f0a6656c077a16cad663e540543a78.pfvmeta: gfid different on subvolume
[2014-03-03 08:30:54.287017] I [afr-self-heal-common.c:1970:afr_sh_post_nb_entrylk_gfid_sh_cbk] 0-bj-mams-replicate-6: Non blocking entrylks failed.
[2014-03-03 08:30:54.287910] W [inode.c:914:inode_lookup] (-->/usr/lib64/glusterfs/3.3.0.5rhs_iqiyi_7/xlator/debug/io-stats.so(io_stats_lookup_cbk+0xff) [0x7fb6fd630adf] (-->/usr/lib64/glusterfs/3.3.0.5rhs_iqiyi_7/xlator/mount/fuse.so(+0xf3f8) [0x7fb7019da3f8] (-->/usr/lib64/glusterfs/3.3.0.5rhs_iqiyi_7/xlator/mount/fuse.so(+0xf25b) [0x7fb7019da25b]))) 0-fuse: inode not found

I saw similar discussion in mail list, but i don't see the solution to fix this issue.
http://www.gluster.org/pipermail/gluster-users/2013-June/036190.html

Using umount and remount, the client is alive now. but What I want know why this happen ? Is there any bugfix on this?
thanks

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users