Thanks Justin. Will it be possible to apply this new version as a rolling update to my servers keeping the volume online? 3.4.1 to 3.4.3-3 shouldn't cause problems with existing clients and other servers, right? I've got a couple of new 50TB JBODs and a test server, just as soon as the rpms are ready I'll give it a test before deploying for real. Cheers, On Mon, 2014-04-14 at 21:35 +0100, Justin Clift wrote: > On 14/04/2014, at 5:45 PM, Justin Clift wrote: > > On 14/04/2014, at 3:40 AM, Franco Broi wrote: > >> Hi Vijay > >> > >> How do I get the fix? I'm running 3.4.1, should I upgrade to a newer > >> version? > >> > >> I need a quick fix, this is causing us a lot of grief. > > > > Looking through the git repository branches, that patch doesn't seem > > to be in 3.4 series (so far). > > > > It's in the 3.5 release series. 3.5.0 isn't released though. :/ > > > Discussed this with Kaleb, who creates the rpms. We can make a 3.4.3-3 > rpm including the above patch (it's a simple 1-liner). > > The patch needs to be reviewed + approved for the release-3.4 branch > first though. Patch review here: > > http://review.gluster.org/#/c/7478/ > > Ran the regression test on a local VM here with the patch added, and > nothing untoward shows up. Hopefully we can get this reviewed, merged, > and out to you in soon-ish timeframe. :) > > Regards and best wishes, > > Justin Clift > > -- > Open Source and Standards @ Red Hat > > twitter.com/realjustinclift > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
