This mostly occurs when you run two gluster commands simultaneously. Gluster uses a lock on each peer to synchronize commands. Any command which would need to do operations on multiple peers, would first acquire this lock, and release it after doing the operation. If a command cannot acquire a lock because another command had the lock, it will fail with the above error message. It sometimes happens that a command could fail to release the lock on some peers. When this happens all further commands which need the lock will fail with the same error. In this case your only option is to restart glusterd on the peers which have the stale lock held. This will not cause any downtime as the brick processes are not affected by restarting glusterd. In your case, since you can run commands on other nodes, most likely you are running commands simultaneously or at least running a command before an old one finishes. ~kaushal On Tue, Mar 18, 2014 at 11:24 AM, Franco Broi <franco.broi@xxxxxxxxxx> wrote: > > What causes this error? And how do I get rid of it? > > [root@nas4 ~]# gluster vol status > Another transaction could be in progress. Please try again after sometime. > > > Looks normal on any other server. > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://supercolony.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
