On Thu, Nov 10, 2011 at 08:57:27AM -0500, Jeff Darcy wrote: > That definitely seems like something that should never happen, so I'd be a bit > concerned. Perhaps more pertinently, ISTRC that some of the code I looked at > in our last round of investigation had to do with inodelk, so there's a decent > chance that they're related. Now I fixed my FUSE emulation, both messages are gone, so they were definitively related. I still have the problem with existing files getting a rare ENOENT, but it takes hours of builds on the glusterfs volume to get the bug to show up. -- Emmanuel Dreyfus manu@xxxxxxxxxx
