Created attachment 1048674 [details] core file Description of problem: ======================= Seen the crash while running IO bringing down some of the bricks and heal is in progress. Backtrace: ========= (gdb) bt #0 0x00007f789fde4718 in __ec_removexattr_sinks ( frame=<value optimized out>, ec=0x7f78a023c0e0, inode=<value optimized out>, source=1, sources=<value optimized out>, healed_sinks=0x7f7840203c70 "", replies=0x7f78401f6a10) at ec-heal.c:611 #1 0x00007f789fde86f9 in __ec_heal_metadata (frame=0x7f78af1df1d4, ec=0x7f78a023c0e0, inode=0x7f78a023ca30, locked_on=0x7f78401f72b8 "", sources=0x7f7840203c90 "", healed_sinks=0x7f7840203c70 "") at ec-heal.c:686 #2 0x00007f789fde8993 in ec_heal_metadata (frame=0x7f78af1df1d4, ec=0x7f78a023c0e0, inode=0x7f78a023ca30, sources=0x7f7840203c90 "", healed_sinks=0x7f7840203c70 "") at ec-heal.c:747 #3 0x00007f789fde8ba0 in ec_heal_do (this=<value optimized out>, data=0x7f789dfb6cfc, loc=0x7f789dfb6f54, partial=0) at ec-heal.c:2264 #4 0x00007f789fde8f7d in ec_synctask_heal_wrap ( opaque=<value optimized out>) at ec-heal.c:2309 #5 0x00007f78b181a1f2 in synctask_wrap (old_task=<value optimized out>) at syncop.c:381 #6 0x00007f78b01828f0 in ?? () from /lib64/libc.so.6 #7 0x0000000000000000 in ?? () (gdb) Version-Release number of selected component (if applicable): ============================================================= [root@interstellar ~]# gluster --version glusterfs 3.7.1 built on Jul 2 2015 21:01:51 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@interstellar ~]# How reproducible: ================= Seen once Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: ================= Attaching the core file.
verified this on 3.7.1-10 build and didn't see the crash. Marking this as fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html