To satisfy this curiosity, however, ubuntu 12.04's
libc6-2.15-0ubuntu10.5 produces:
objdump -r -d /lib/x86_64-linux-gnu/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.")
Your libc looks OK.
On 02/23/2016 07:53 AM, Krutika
Dhananjay wrote:
Raghavendra,
The crash was due to bug(s) in clear-locks command
implementation. Joe and I had had an offline discussion about
this.
-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 giv
en 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,
|
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
