On 09/07/2014 10:01 AM, Emmanuel Dreyfus wrote: > How am I supposed to address this? > > # gluster volume status gfs352 > Another transaction is in progress. Please try again after sometime. > > Retrying after some time does not help. The glusterd log file at least > tells me who the culprit is: > [2014-09-07 04:20:25.820379] E [glusterd-utils.c:153:glusterd_lock] > 0-management: Unable to get lock for uuid: > 078015de-2186-4bd7-a4d1-017e39c16dd3, lock held by: > 078015de-2186-4bd7-a4d1-017e39c16dd3 > > This UUID is a brick whose log file will not tell anything particular. This means that the glusterd daemon running on that node is holding the lock. Looking at the log, I believe you are running 3.5 version bits or less as 3.6 and onwards the locking mechanism has been enhanced on per volume basis instead of per node basis. 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. ~Atin > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
