Derek Yarnell
2015-May-22 13:52 UTC
[Gluster-users] Upgrade to 3.7.0 with transaction lock issues
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 -- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies
Atin Mukherjee
2015-May-22 14:09 UTC
[Gluster-users] Upgrade to 3.7.0 with transaction lock issues
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 lockThis 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>
Sergio Traldi
2015-Jun-10 08:11 UTC
[Gluster-users] Upgrade to 3.7.0 with transaction lock issues
Derek Yarnell <derek at ...> writes:> > 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 >Hi all, I two servers with 3.7.1 and have the same problem with 3.7.1: # rpm -qa | grep gluster | sort glusterfs-3.7.1-1.el6.x86_64 glusterfs-api-3.7.1-1.el6.x86_64 glusterfs-cli-3.7.1-1.el6.x86_64 glusterfs-client-xlators-3.7.1-1.el6.x86_64 glusterfs-fuse-3.7.1-1.el6.x86_64 glusterfs-geo-replication-3.7.1-1.el6.x86_64 glusterfs-libs-3.7.1-1.el6.x86_64 glusterfs-server-3.7.1-1.el6.x86_64 # gluster volume status Another transaction is in progress. Please try again after sometime. and in the log I found: [2015-06-09 16:12:38.949842] E [glusterd-utils.c:164:glusterd_lock] 0-management: Unable to get lock for uuid: 99a41a2a-2ce5-461c-aec0-510bd5b37bf2, lock held by: 04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c [2015-06-09 16:12:38.949864] E [glusterd-syncop.c:1766:gd_sync_task_begin] 0-management: Unable to acquire lock I check the file:>From server 1:# cat /var/lib/glusterd/peers/04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c uuid=04a7d2bb-bdd9-4e0d-b460-87ad4adbe12c state=3 hostname1=192.168.61.101>From server 2:# cat /var/lib/glusterd/peers/99a41a2a-2ce5-461c-aec0-510bd5b37bf2 uuid=99a41a2a-2ce5-461c-aec0-510bd5b37bf2 state=3 hostname1=192.168.61.100 And they seems correct. Any hint? Cheers Sergio