<p dir="ltr"></p>
<p dir="ltr">Regards,<br>
Atin</p>
<p dir="ltr">Sent from Samsung Galaxy S4<br>
On 22 May 2015 19:22, "Derek Yarnell" <<a href="mailto:derek@umiacs.umd.edu">derek@umiacs.umd.edu</a>> wrote:<br>
><br>
> We just upgraded to 3.7.0 from 3.4.2 last night (no quotas, no geosync)<br>
> and the volume came up and is available via NFS. But we can't get<br>
> status for the volume or any other administration. We have restarted<br>
> all the gluster daemons on both nodes in the cluster multiple times.<br>
><br>
> gluster> volume status<br>
> Another transaction is in progress. Please try again after sometime.<br>
><br>
> [2015-05-22 13:46:49.309316] E [glusterd-utils.c:164:glusterd_lock]<br>
> 0-management: Unable to get lock for uuid:<br>
> b01d12b9-e2a1-400a-a3ad-1018dead6e65, lock held by:<br>
> b01d12b9-e2a1-400a-a3ad-1018dead6e65<br>
> [2015-05-22 13:46:49.309382] E<br>
> [glusterd-syncop.c:1736:gd_sync_task_begin] 0-management: Unable to<br>
> acquire lock<br>
This is a known issue with the latest build of 3.7. It will get resolved in 3.7.1. Alternatively you can also apply <a href="http://review.gluster.org/#/c/10842/">http://review.gluster.org/#/c/10842/</a> if you can download the source and proceed with rebuild.<br>
><br>
> --<br>
> Derek T. Yarnell<br>
> University of Maryland<br>
> Institute for Advanced Computer Studies<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</p>