Hide Forgot
You do simple tests with ASAN??? [root@xintel2 ~]# rpm -qa | grep gluster vdsm-gluster-4.18.11-1.el7.centos.noarch glusterfs-libs-3.8.2-1.el7.x86_64 nfs-ganesha-gluster-2.3.3-1.el7.x86_64 glusterfs-cli-3.8.2-1.el7.x86_64 glusterfs-client-xlators-3.8.2-1.el7.x86_64 glusterfs-server-3.8.2-1.el7.x86_64 glusterfs-geo-replication-3.8.2-1.el7.x86_64 glusterfs-api-3.8.2-1.el7.x86_64 python-gluster-3.8.2-1.el7.noarch glusterfs-debuginfo-3.7.13-1.el7.x86_64 glusterfs-fuse-3.8.2-1.el7.x86_64 glusterfs-3.8.2-1.el7.x86_64 glusterfs-ganesha-3.8.2-1.el7.x86_64 *** Error in `/usr/bin/ganesha.nfsd': munmap_chunk(): invalid pointer: 0x000060700000a7b0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7b194)[0x7f90f700f194] /lib64/libglusterfs.so.0(_gf_log+0x23e)[0x7f90f24e2d8e] /usr/lib64/glusterfs/3.8.2/rpc-transport/socket.so(+0x8ddf)[0x7f90e4994ddf] /usr/lib64/glusterfs/3.8.2/rpc-transport/socket.so(+0x917f)[0x7f90e499517f] /lib64/libglusterfs.so.0(+0x82b00)[0x7f90f253bb00] /lib64/libpthread.so.0(+0x7dc5)[0x7f90f79bcdc5] /lib64/libc.so.6(clone+0x6d)[0x7f90f708aced] ======= Memory map: ======== 7fff7000-8fff7000 rw-p 00000000 00:00 0 8fff7000-2008fff7000 ---p 00000000 00:00 0
https://github.com/gluster/glusterfs/pull/49
As mentioned in the https://bugzilla.redhat.com/show_bug.cgi?id=1368739#c2, could you re-test with upcall off
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.