----- Original Message ----- > Hi, > > We've been using GlusterFS 3.4.0 on Debian 7 for around 11 months. Every so > often (once every 6 weeks or so) a server running the client and nginx > accessing the gluster storage would suffer a hard lockup of nginx and > require a reboot. This wasn't such a big deal as there were several clients > so there was never a loss to production. > > However in the last few days we've seen a huge increase in these lockups. > Perhaps 2-3 times a day on multiple machines. > > The bug appears to be very similar to > https://bugzilla.redhat.com/show_bug.cgi?id=764743 from Gluster 3.2 and the > suggestion of first killing the Gluster process does allow a restart of > nginx without a reboot. > > The only changes to our usage of late have been to stop a rebalance process > (as we're at the point where we need to add extra bricks) and to breach 80% > usage on the volume (Total volume size is 400TB). > > Has anyone else had any experience of this bug re-emerging in Gluster 3.4? As a side thought, how practical would it be to upgrade to GlusterFS 3.4.5? There have been a lot of bug fixes (some pretty important) between 3.4.0, and 3.4.5. I have no idea if there's a fix for the problem you mention in there btw, I'm just asking in general. :) Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
