On 1 Apr 2015, at 19:47, Jeff Darcy <jdarcy@xxxxxxxxxx> wrote: >> When doing an initial burn in test (regression run on master head >> of GlusterFS git), it coredumped on the new "slave23.cloud.gluster.org" VM. >> (yeah, I'm reusing VM names) >> >> http://build.gluster.org/job/regression-test-burn-in/16/console >> >> Does anyone have time to check the coredump, and see if this is >> the bug we already know about? > > This is *not* the same as others I've seen. There are no threads in the > usual connection-cleanup/list_del code. Rather, it looks like some are > in generic malloc code, possibly indicating some sort of arena corruption. Is it ok to put slave23.cloud.gluster.org into general rotation, so it runs regression jobs along with the rest? + Justing -- 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-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
