+++ This bug was initially created as a clone of Bug #1226272 +++ Description of problem: Volume heal info core dumps when there is qemu-block. Version-Release number of selected component (if applicable): gluster-3.7.0 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Core dump with below trace: Program terminated with signal 11, Segmentation fault. #0 inode_unref (inode=0x7f7a1e27806c) at inode.c:499 499 table = inode->table; (gdb) bt #0 inode_unref (inode=0x7f7a1e27806c) at inode.c:499 #1 0x00007f7a265e8a61 in fini (this=<optimized out>) at qemu-block.c:1092 #2 0x00007f7a39a53791 in xlator_fini_rec (xl=0x7f7a2000b9a0) at xlator.c:463 #3 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a2000d450) at xlator.c:453 #4 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a2000e800) at xlator.c:453 #5 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a2000fbb0) at xlator.c:453 #6 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a20010f80) at xlator.c:453 #7 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a20012330) at xlator.c:453 #8 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a200136e0) at xlator.c:453 #9 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a20014b30) at xlator.c:453 #10 0x00007f7a39a53725 in xlator_fini_rec (xl=0x7f7a20015fc0) at xlator.c:453 #11 0x00007f7a39a54eea in xlator_tree_fini (xl=<optimized out>) at xlator.c:545 #12 0x00007f7a39a90b25 in glusterfs_graph_deactivate (graph=<optimized out>) at graph.c:340 #13 0x00007f7a38d50e3c in pub_glfs_fini (fs=fs@entry=0x7f7a3a6b6010) at glfs.c:1155 #14 0x00007f7a39f18ed4 in main (argc=<optimized out>, argv=<optimized out>) at glfs-heal.c:821 Expected results: No crash Additional info:
REVIEW: http://review.gluster.org/11002 (features/qemu-block: Don't unref root inode) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11002 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 35f7d213fe7395ba502a8e209b04c2be1ea75928 Author: Pranith Kumar K <pkarampu> Date: Fri May 29 16:28:10 2015 +0530 features/qemu-block: Don't unref root inode Root inode doesn't participate in ref/unref. Don't do it in fini as by the time fini is called itable would be destroyed. BUG: 1226276 Change-Id: I704d0a3c0813cb8f6c3f1f7d613c89aca8f4f9ad Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11002 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
REVIEW: http://review.gluster.org/11076 (features/qemu-block: Add comment about root_inode handling) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/11076 (features/qemu-block: Add comment about root_inode handling) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/11076 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit eeccafc72c95da83abeb51966d7eeeab02190899 Author: Pranith Kumar K <pkarampu> Date: Thu Jun 4 08:21:59 2015 +0530 features/qemu-block: Add comment about root_inode handling This is handling the comment on 3.7 backport http://review.gluster.com/11047 Change-Id: I253a8e0bfebde63f25c839efd55ed3cc30e6cd9b BUG: 1226276 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11076 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Poornima G <pgurusid>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user