On 09/07/2014 12:43 PM, Emmanuel Dreyfus wrote: > Atin Mukherjee <amukherj@xxxxxxxxxx> wrote: > >> I suggest you should check the glusterd log file at node >> 078015de-2186-4bd7-a4d1-017e39c16dd3, if you don't find the reason of >> why glusterd did not release the lock work around will be to restart >> glusterd there. > > I still have the message after a glusterd restart. I will try with > release-3.6 Can you restart the originator glusterd node as well? ~Atin > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
