Here is an update to this issue. Gaurav Garg (In Cc) has identified the
root cause and the fix [1] has been posted for review in mainline. Once
its merged we will backport it and push it for 3.7.6.
The issue originated because of introducing new enums in the middle of
the enum structure which resu
I have filed a bug for this on bugzilla.
Here is the link https://bugzilla.redhat.com/show_bug.cgi?id=1276029.
Please cc yourself for updates on the bug.
Thanks,
Raghavendra Talur
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.glus
I have replicated my upgradable environment in a testing lab with the
following configuration:
Distributed gluster (one brick per node)
- Node gluster-1: glusterfs version 3.7.4
- Node gluster-2: glusterfs version 3.7.4
- Node gluster-3: glusterfs version 3.7.4
I began by upgrading only the first
Hi,
We're debating updating from 3.5.x to 3.7.x soon on our 2x2 replica set and
these upgrade issues are a bit worrying. Can I hear a few voices from
people who have had positive experiences? :)
Thanks,
Alan
On Fri, Oct 23, 2015 at 6:32 PM, JuanFra Rodríguez Cardoso <
jfrodrig...@keedio.com> wr
I had that problem too, but I'm not able to fix it. I was forced to
downgrade to 3.7.4 to continue running my gluster volumes.
The upgrading process (3.7.4 -> 3.7.5) does not seem fully reliable.
Best.
.
Juan Francisco Rodrígue
Hi David,
The logs you attached, are they from node "frackib01.corvidtec.com", if
not can you attach logs from the node "frackib01.corvidtec.com" ?
Regards
Rafi KC
On 10/16/2015 05:46 PM, David Robinson wrote:
> I have a replica pair setup that I was trying to upgrade from 3.7.4 to
> 3.7.5.
> Af
