[Gluster-users] Need urgent help to downgrade 3.7.12 to 3.7.11

[Kaushal M]

You need to edit the `/var/lib/glusterd/glusterd.info` manually on all
the nodes to reduce the op-version. Set it to the version you want,
and start glusterd.
 Make sure you edit the file on all nodes before starting even one glusterd.

On Wed, Jun 29, 2016 at 6:03 PM, Lindsay Mathieson
<lindsay.mathieson at gmail.com> wrote:
> My 3.7.12 upgrade has rendered my vm cluster unusable and I urgently need to
> downgrade to a working version.
>
>
> I can't set the op-version back from 30712 to 30710, I get error:
>
> gluster v set all  op-version 30710
> volume set: failed: Required op-version (30710) should not be equal or lower
> than current cluster op-version (30712)
>
>
> If I revert the gluster packages to 3.7.11 then the gluster servcie refuses
> to start.
>
>
> BTW, current settings are:
>
>
> Volume Name: datastore4
> Type: Replicate
> Volume ID: 0ba131ef-311d-4bb1-be46-596e83b2f6ce
> Status: Started
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: vnb.proxmox.softlog:/tank/vmdata/datastore4
> Brick2: vng.proxmox.softlog:/tank/vmdata/datastore4
> Brick3: vna.proxmox.softlog:/tank/vmdata/datastore4
> Options Reconfigured:
> cluster.background-self-heal-count: 16
> cluster.self-heal-window-size: 1024
> performance.readdir-ahead: on
> features.shard: on
> cluster.quorum-type: auto
> cluster.server-quorum-type: server
> nfs.disable: on
> nfs.addr-namelookup: off
> nfs.enable-ino32: off
> performance.strict-write-ordering: off
> performance.stat-prefetch: on
> performance.quick-read: off
> performance.read-ahead: off
> performance.io-cache: off
> cluster.eager-lock: enable
> network.remote-dio: enable
> features.shard-block-size: 64MB
> cluster.locking-scheme: full
>
>
>
>
> --
> Lindsay Mathieson
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users