|author||Raghavendra G <firstname.lastname@example.org>||2012-05-14 14:23:56 +0530|
|committer||Anand Avati <email@example.com>||2012-08-03 01:13:36 -0700|
mount/fuse: ignore any erros that might've happened while resolving entry in resolver.
One error we hit was absence of gfid on backend. While the lookup code-path generates a new uuid and sets it on file, resolver code doesn't do that. Since, functionally (atleast after resolving parent inode, we would be resolving the path in new-graph) both resolver and lookup does same work, it would be no harm in ignoring errors during resolving the entry. This would help us to continue with the _extra_ work (like healing gfid as of now) in fuse_lookup_resume. Change-Id: If46d5e07c32e67b5744287a6ef55d0b0fe347689 BUG: 821138 Signed-off-by: Raghavendra G <firstname.lastname@example.org> Reviewed-on: http://review.gluster.com/3344 Tested-by: Gluster Build System <email@example.com> Reviewed-by: Anand Avati <firstname.lastname@example.org>
Diffstat (limited to 'libglusterfs/src/globals.h')
0 files changed, 0 insertions, 0 deletions