On 05/18/2015 11:47 AM, Emmanuel Dreyfus wrote: > Krishnan Parthasarathi <kparthas@xxxxxxxxxx> wrote: > >> Could you provide the set of commands that were issued >> before you started observing volume-status command isn't working? > > I just upgraded from 3.6.x. After restarting the service, I tried > gluster volume status to check everything was alright and it never > passed because of other transaction in progress. Another transaction is in progress indicates that there is lock held on the volume for which status request was issued and it sounds strange. Were you running a single node cluster, if not were you running any other commands from the other nodes? Do you have a setup where the problem is reproducible? If so I would like to have a look at it. > -- ~Atin _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
