On Thu, Nov 10, 2011 at 1:56 PM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
Considering it came in 'setlk()', this may not be completely harmless. Also, if you see that log, user's systemcall will get an error for sure.
-Amar
Hi
I am still tracking my bug on randomly ENOENT for existing files.
I notice this rare error in the client logs:
[2011-11-10 08:18:20.170776] E [fuse-bridge.c:2840:fuse_setlk_resume]
0-glusterfs-fuse: xl is NULL
This means after a graph switch we are not able to find the translator for the 'fd/inode'.
Is it something of concern, or is it harmless?
Considering it came in 'setlk()', this may not be completely harmless. Also, if you see that log, user's systemcall will get an error for sure.
-Amar
