+++ This bug was initially created as a clone of Bug #847214 +++ Description of problem: Did a volume set operation while the other peers in the cluster were down. Op-sm hung. Op-sm is stuck in an infinite state-transition: Old State: [Ack drain] New State: [Ack drain] Event : [GD_OP_EVENT_START_UNLOCK] timestamp: [2012-08-10 06:10:25] Old State: [Ack drain] New State: [Ack drain] Event : [GD_OP_EVENT_START_UNLOCK] timestamp: [2012-08-10 06:10:28] Old State: [Ack drain] New State: [Ack drain] Event : [GD_OP_EVENT_START_UNLOCK] timestamp: [2012-08-10 06:10:28] Old State: [Ack drain] New State: [Ack drain] Event : [GD_OP_EVENT_START_UNLOCK] timestamp: [2012-08-10 06:10:31] Old State: [Ack drain] New State: [Ack drain] Event : [GD_OP_EVENT_START_UNLOCK] timestamp: [2012-08-10 06:10:31] Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: This the setup in which I got the problem, but I think it can be triggered even with 2 machines 1.Have a cluster with 3 machines. 2.Bring two of the glusterds down. 3.Execute any glusterd operation command which uses op-sm, I used volume set. Actual results: The operation will hang after commit-op. Expected results: volume set operation should have been successful. Additional info:
*** Bug 861919 has been marked as a duplicate of this bug. ***
*** Bug 860568 has been marked as a duplicate of this bug. ***
http://review.gluster.org/4297 is a base need for this to get fixed. Will fix 'all' the commands once this gets fixed for volume status.
*** Bug 852295 has been marked as a duplicate of this bug. ***
CHANGE: http://review.gluster.org/4295 (glusterd: Moved node rsp functions to glusterd-utils.c) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4296 (glusterd: Added syncop version of BRICK_OP) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4297 (glusterd: Made volume-status use synctask framework) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4494 (glusterd: Made volume-statedump use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4492 (glusterd: Made volume-delete use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4491 (glusterd: Made volume-stop use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4490 (glusterd : Made volume clear-locks use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4489 (glusterd: Made volume-sync use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4488 (glusterd : Made volume-set use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4474 (glusterd: Making volume-reset use synctask framework) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4473 (glusterd: Made gsync set use synctask framework) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4478 (glusterd: Made log-rotate use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4495 (glusterd: Made volume-quota use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4493 (glusterd: Made volume-heal use synctask framework.) merged in master by Anand Avati (avati)
CHANGE: http://review.gluster.org/4507 (glusterd: Made gd_synctask_begin less 'monolithic' in terms of LOC.) merged in master by Anand Avati (avati)
Verified on: glusterfs 3.4.0.14rhs built on Jul 30 2013 09:09:36
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html