<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On Jul 6, 2015 7:45 PM, "Alun James" <<a href="mailto:ajames@tibus.com">ajames@tibus.com</a>> wrote:<br>
><br>
> Ok thanks. I see this:<br>
><br>
> Unable to get lock for uuid: 06a089b9-01d8-48c1-b02c-fa051897ab45, lock held by: 749ac41e-6d00-4d3c-9fb8-55b73135b4ee<br>
><br>
> I have tried gluster vol status on node 749ac41e-6d00-4d3c-9fb8-55b73135b4ee too, however it giving:<br>
><br>
> gluster vol status<br>
><br>
> Locking failed on my-web01. Please check log file for details.<br>
> Locking failed on my-web02. Please check log file for details.<br>
This means something is wrong on my-web02. As a work around request you to restart glusterd service on all the nodes.<br>
><br>
><br>
> ________________________________<br>
> From: "Atin Mukherjee" <<a href="mailto:atin.mukherjee83@gmail.com">atin.mukherjee83@gmail.com</a>><br>
> To: "Alun James" <<a href="mailto:ajames@tibus.com">ajames@tibus.com</a>><br>
> Cc: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Sent: Monday, 6 July, 2015 3:07:57 PM<br>
> Subject: Re: [Gluster-users] volume command issues<br>
><br>
><br>
> -Atin<br>
> Sent from one plus one<br>
> On Jul 6, 2015 7:30 PM, "Alun James" <<a href="mailto:ajames@tibus.com">ajames@tibus.com</a>> wrote:<br>
> ><br>
> > Hi folks,<br>
> ><br>
> > I have a 3 node gluster volume that developed a problem with gluster vol commands e.g. gluster vol status<br>
> ><br>
> > GlusterFS version 3.6.2<br>
> ><br>
> > The volume is successfully mounted and appears to be working correctly (for now).<br>
> ><br>
> > gluster volume info<br>
> ><br>
> > Volume Name: my_filestore_vol<br>
> > Type: Replicate<br>
> > Volume ID: ....<br>
> > Status: Started<br>
> > Number of Bricks: 1 x 3 = 3<br>
> > Transport-type: tcp<br>
> > Bricks:<br>
> > Brick1: my-web01:/export/brick0<br>
> > Brick2: my-web02:/export/brick0<br>
> > Brick3: my-web03:/export/brick0<br>
> > Options Reconfigured:<br>
> > nfs.drc: off<br>
> > diagnostics.brick-log-level: WARNING<br>
> ><br>
> > gluster volume status<br>
> ><br>
> > Another transaction is in progress. Please try again after sometime.<br>
> This indicates one more command has acquired the lock on the same volume. Please check etc-glusterfs-*.log (glusterd log) to see which node has acquired the volume lock. cmd_history.log file will also hint you the other concurrent command ran.<br>
> ><br>
> > I am also seeing errors in the self-heal logs...<br>
> ><br>
> > /var/log/glusterfs/glfsheal-my_filestore_vol.log<br>
> ><br>
> > [2015-07-06 13:49:12.609285] E [glfs-mgmt.c:520:mgmt_getspec_cbk] 0-gfapi: failed to get the 'volume file' from server<br>
> > [2015-07-06 13:49:12.609331] E [glfs-mgmt.c:599:mgmt_getspec_cbk] 0-glfs-mgmt: failed to fetch volume file (key:my_filestore_vol)<br>
> > [2015-07-06 13:49:27.377875] E [glfs-mgmt.c:520:mgmt_getspec_cbk] 0-gfapi: failed to get the 'volume file' from server<br>
> > [2015-07-06 13:49:27.377928] E [glfs-mgmt.c:599:mgmt_getspec_cbk] 0-glfs-mgmt: failed to fetch volume file (key:my_filestore_vol)<br>
> > [2015-07-06 13:50:21.963651] E [glfs-mgmt.c:520:mgmt_getspec_cbk] 0-gfapi: failed to get the 'volume file' from server<br>
> > [2015-07-06 13:50:21.963710] E [glfs-mgmt.c:599:mgmt_getspec_cbk] 0-glfs-mgmt: failed to fetch volume file (key:my_filestore_vol)<br>
> ><br>
> > Has anyone experienced similar?<br>
> ><br>
> > ALUN JAMES<br>
> > Senior Systems Engineer<br>
> > Tibus<br>
> ><br>
> > T: +44 (0)28 9033 1122<br>
> > E: <a href="mailto:ajames@tibus.com">ajames@tibus.com</a><br>
> > W: <a href="http://www.tibus.com">www.tibus.com</a><br>
> ><br>
> > Follow us on Twitter @tibus<br>
> ><br>
> > Tibus is a trading name of The Internet Business Ltd, a company limited by share capital and registered in Northern Ireland, NI31235. It is part of UTV Media Plc.<br>
> ><br>
> > This email and any attachment may contain confidential information for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorised to receive for the recipient), please contact the sender by reply email and delete all copies of this message. <br>
> ><br>
> > _______________________________________________<br>
> > Gluster-users mailing list<br>
> > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> > <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
><br>
><br>
</p>