Gluster users - Jun 2015 - can't remove brick - wrong operating-version

Hi All,

I'm hitting what seems to be a known but unresolved bug, exactly similar to
these:


Most recently:

https://bugzilla.redhat.com/show_bug.cgi?id=1168897


Similar from some time ago:

https://bugzilla.redhat.com/show_bug.cgi?id=1127328


Essentially the upshot is that the remove-brick operation reports:


volume remove-brick commit force: failed: One or more nodes do not support the
required op-version. Cluster op-version must atleast be 30600.


I'm on CentOS 6.6 with GlusterFS 3.6.3 from glusterfs-epel. The
operating-version in /var/lib/glusterd/glusterd.info is set to 2 on all hosts
participating in the volume.


I see that some recommend manually changing that setting in glusterd.info to
something higher than 30600, but that does not seem particularly safe, and a
Ubuntu 14.04 user reported that glusterd wouldn't actually start when that
setting was changed.


Is there any workaround to this? I can't imagine everyone in the world
running Gluster is unable to remove bricks at the moment ...


Thanks in advance for any insight you can provide.


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20150602/bb22803a/attachment.html>

Sent from Samsung Galaxy S4
On 3 Jun 2015 01:17, "Branden Timm" <btimm at wisc.edu>
wrote:
>
> Hi All,
>
> I'm hitting what seems to be a known but unresolved bug, exactly
similar
to these:
>
>
> Most recently:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1168897
>
>
> Similar from some time ago:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1127328
>
>
> Essentially the upshot is that the remove-brick operation reports:
>
>
> volume remove-brick commit force: failed: One or more nodes do not
support the required op-version. Cluster op-version must atleast be
30600.
>
>
> I'm on CentOS 6.6 with GlusterFS 3.6.3 from glusterfs-epel. The
operating-version in /var/lib/glusterd/glusterd.info is set to 2 on all
hosts participating in the volume.
>
>
> I see that some recommend manually changing that setting in glusterd.info
to something higher than 30600, but that does not seem particularly safe,
and a Ubuntu 14.04 user reported that glusterd wouldn't actually start when
that setting was changed.
>
>
> Is there any workaround to this? I can't imagine everyone in the world
running Gluster is unable to remove bricks at the moment
...
>
>
> Thanks in advance for any insight you can provide.
>
Could you execute gluster volume set all cluster.op-version 30600? This
should bump up the cluster op-version which will ideally persist the value
in glusterd.info file. Post that you should be able to execute remove brick
command.

HTH,
Atin
>
>
>
> _______________________________________________
> 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/20150603/421aaaa7/attachment.html>