ugh never mind,
I see the other thread.
On 6/29/2016 11:55 AM, WK wrote:
glad you are back up but what was the issue?
was it a function of the upgrade or something wrong with 3.7.12
-wk
On 6/29/2016 7:35 AM, Lindsay Mathieson wrote:
On 29/06/2016 11:27 PM, Kaushal M wrote:
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.
Well I've got my cluster back up and running, with no apparent
damage. I had to revert to op-version 30710 *and* roll the package
versions back to 3.7.11
I did try 3.7.12/op-version 30710, but it had the same issues as
noted before.
Thanks all for the help, I was really sweating it for a bit there.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
