----- Original Message ----- > From: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx> > To: "Raghavendra G" <raghavendra@xxxxxxxxxxx> > Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Tuesday, February 23, 2016 9:23:33 PM > Subject: Re: 3.6.8 crashing a lot in production > > Raghavendra, > > The crash was due to bug(s) in clear-locks command implementation. Joe and I > had had an offline discussion about this. oh! Thanks for the update :). > > -Krutika > > > > From: "Raghavendra G" <raghavendra@xxxxxxxxxxx> > To: "Krutika Dhananjay" <kdhananj@xxxxxxxxxx> > Cc: "Joe Julian" <joe@xxxxxxxxxxxxxxxx>, "Gluster Devel" > <gluster-devel@xxxxxxxxxxx> > Sent: Tuesday, February 23, 2016 8:54:01 PM > Subject: Re: 3.6.8 crashing a lot in production > > Came across a glibc bug which could've caused some corruptions. On googling > about possible problems, we found that there is an issue ( > https://bugzilla.redhat.com/show_bug.cgi?id=1305406 ) fixed in > glibc-2.17-121.el7. From the bug we found the following test-script to > determine if the glibc is buggy. And on running it, we ran it on the local > setup using the following method given in the bug: > ---------------- # objdump -r -d /lib64/libc.so.6 | grep -C 20 _int_free | > grep -C 10 cmpxchg | head -21 | grep -A 3 cmpxchg | tail -1 | (grep '%r' && > echo "Your libc is likely buggy." || echo "Your libc looks OK.") 7cc36: 48 > 85 c9 test %rcx,%rcx Your libc is likely buggy. ---------------- Could you > check if the above command on your setup gives the same output which says > "Your libc is likely buggy." regards, > > On Sat, Feb 13, 2016 at 7:46 AM, Krutika Dhananjay < kdhananj@xxxxxxxxxx > > wrote: > > > > Taking a look. Give me some time. > > -Krutika > > > > > From: "Joe Julian" < joe@xxxxxxxxxxxxxxxx > > To: "Krutika Dhananjay" < kdhananj@xxxxxxxxxx >, gluster-devel@xxxxxxxxxxx > Sent: Saturday, February 13, 2016 6:02:13 AM > Subject: Fwd: 3.6.8 crashing a lot in production > > > Could this be a regression from http://review.gluster.org/7981 ? > > -------- Forwarded Message -------- Subject: 3.6.8 crashing > a lot in production > Date: Fri, 12 Feb 2016 16:20:59 -0800 > From: Joe Julian <joe@xxxxxxxxxxxxxxxx> > > To: gluster-users@xxxxxxxxxxx , gluster-devel@xxxxxxxxxxx > > > I have multiple bricks crashing in production. Any help would be greatly > appreciated. > > The crash log is in this bug report: > https://bugzilla.redhat.com/show_bug.cgi?id=1307146 Looks like it's crashing > in pl_inodelk_client_cleanup > _______________________________________________ > Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > > > > -- > Raghavendra G > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
