[Bugs] [Bug 1262324] New: Data Tiering:glusterd crashes while attaching tier

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1262324

            Bug ID: 1262324
           Summary: Data Tiering:glusterd crashes while attaching tier
           Product: GlusterFS
           Version: 3.7.4
         Component: tiering
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
=====================
I was doing an attach tier whithout any IOs and the glusterd crashed

Following is the BT:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/sbin/glusterd -p /var/run/glusterd.pid'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007f96812593e9 in rpc_transport_submit_request ()
   from /lib64/libgfrpc.so.0
Missing separate debuginfos, use: debuginfo-install
glusterfs-server-3.7.4-0.27.git143f0f9.el7.centos.x86_64
(gdb) bt
#0  0x00007f96812593e9 in rpc_transport_submit_request ()
   from /lib64/libgfrpc.so.0
#1  0x00007f9681254a49 in rpcsvc_callback_submit () from /lib64/libgfrpc.so.0
#2  0x00007f9675f4b26d in glusterd_fetchspec_notify ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#3  0x00007f9675ffc2ea in glusterd_op_perform_add_bricks ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#4  0x00007f9675ffe3c0 in glusterd_op_add_brick ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#5  0x00007f9675f7b09b in glusterd_op_commit_perform ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#6  0x00007f9676004a49 in gd_commit_op_phase ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#7  0x00007f967600602d in gd_sync_task_begin ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#8  0x00007f9676006300 in glusterd_op_begin_synctask ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#9  0x00007f9675ff9c68 in __glusterd_handle_add_brick ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#10 0x00007f9675f65de0 in glusterd_big_locked_handler ()
   from /usr/lib64/glusterfs/3.7.4/xlator/mgmt/glusterd.so
#11 0x00007f96814d0d72 in synctask_wrap () from /lib64/libglusterfs.so.0
#12 0x00007f967fb8f0f0 in ?? () from /lib64/libc.so.6
#13 0x0000000000000000 in ?? ()



Version-Release number of selected component (if applicable):
============================================================
[root at zod log]# rpm -qa|grep gluster
glusterfs-client-xlators-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-cli-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-libs-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-api-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-fuse-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-server-3.7.4-0.27.git143f0f9.el7.centos.x86_64
glusterfs-3.7.4-0.27.git143f0f9.el7.centos.x86_64
[root at zod log]# gluster --version
glusterfs 3.7.4 built on Sep  9 2015 01:30:47
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.





Steps to Reproduce:
=====================
1.created a tier volume with hot tier as 2-brick distribute over cold tier of
2x2 with two nodes
2.started volume
3.mounted on both fuse and nfs
4.created a 1gb file from each mnt point
5. attached a tier, which asked for confirmation, and I said "yes"

Then the glusterd crashed immediatley on the localhost where the command was
being executed

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.