[Gluster-users] Upgrade to 3.7.0 with transaction lock issues

[Atin Mukherjee]

Regards,
Atin

Sent from Samsung Galaxy S4
On 22 May 2015 19:22, "Derek Yarnell" <derek at umiacs.umd.edu> wrote:
>
> We just upgraded to 3.7.0 from 3.4.2 last night (no quotas, no geosync)
> and the volume came up and is available via NFS.  But we can't get
> status for the volume or any other administration.  We have restarted
> all the gluster daemons on both nodes in the cluster multiple times.
>
> gluster> volume status
> Another transaction is in progress. Please try again after sometime.
>
> [2015-05-22 13:46:49.309316] E [glusterd-utils.c:164:glusterd_lock]
> 0-management: Unable to get lock for uuid:
> b01d12b9-e2a1-400a-a3ad-1018dead6e65, lock held by:
> b01d12b9-e2a1-400a-a3ad-1018dead6e65
> [2015-05-22 13:46:49.309382] E
> [glusterd-syncop.c:1736:gd_sync_task_begin] 0-management: Unable to
> acquire lock
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
http://review.gluster.org/#/c/10842/ if you can download the source and
proceed with rebuild.
>
> --
> Derek T. Yarnell
> University of Maryland
> Institute for Advanced Computer Studies
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150522/f62177c2/attachment.html>