Description of problem: ====================== I tried to attach a tier with replica count as 10 with one brick and this caused the glusterd to crash gluster v info Connection failed. Please check if gluster daemon is operational. [2015-04-24 10:42:12.496850] I [glusterd-brick-ops.c:1104:glusterd_op_perform_add_bricks] 0-management: replica-count is set 10 [2015-04-24 10:42:12.496869] I [glusterd-brick-ops.c:1108:glusterd_op_perform_add_bricks] 0-management: type is set 5, need to change it The message "I [MSGID: 106006] [glusterd-svc-mgmt.c:327:glusterd_svc_common_rpc_notify] 0-management: quotad has disconnected from glusterd." repeated 34 times between [2015-04-24 10:40:28.174251] and [2015-04-24 10:42:10.199015] The message "I [MSGID: 106006] [glusterd-snapd-svc.c:379:glusterd_snapdsvc_rpc_notify] 0-management: snapd has disconnected from glusterd." repeated 139 times between [2015-04-24 10:40:28.174200] and [2015-04-24 10:42:11.199308] pending frames: frame : type(0) op(0) patchset: git://git.gluster.com/glusterfs.git signal received: 11 time of crash: 2015-04-24 10:42:12 configuration details: argp 1 backtrace 1 dlfcn 1 libpthread 1 llistxattr 1 setfsid 1 spinlock 1 epoll.h 1 xattr.h 1 st_atim.tv_nsec 1 package-string: glusterfs 3.7dev /lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xb2)[0x7f522509ffa2] /lib64/libglusterfs.so.0(gf_print_trace+0x32d)[0x7f52250b80cd] /lib64/libc.so.6(+0x35650)[0x7f5223a94650] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x9468c)[0x7f5219ed468c] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x99d35)[0x7f5219ed9d35] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x9a00b)[0x7f5219eda00b] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x93c12)[0x7f5219ed3c12] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(+0x941f4)[0x7f5219ed41f4] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(generate_client_volfiles+0x12a)[0x7f5219edbb4a] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_create_volfiles+0x29)[0x7f5219edc8c9] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_create_volfiles_and_notify_services+0x1b)[0x7f5219edc97b] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_perform_add_bricks+0x63f)[0x7f5219f06cef] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_add_brick+0x1cf)[0x7f5219f089df] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_commit_perform+0x6b3)[0x7f5219e98813] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(gd_commit_op_phase+0xb6)[0x7f5219f0e416] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(gd_sync_task_begin+0x749)[0x7f5219f0f719] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_op_begin_synctask+0x2c)[0x7f5219f0f78c] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(__glusterd_handle_add_brick+0x4e5)[0x7f5219f057b5] /usr/lib64/glusterfs/3.7dev/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x30)[0x7f5219e861f0] /lib64/libglusterfs.so.0(synctask_wrap+0x12)[0x7f52250da182] /lib64/libc.so.6(+0x470f0)[0x7f5223aa60f0] --------- Version-Release number of selected component (if applicable): ============================================================ glusterfs 3.7dev built on Apr 17 2015 14:27:16 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. glusterfs-api-3.7dev-0.1009.git8b987be.el7.centos.x86_64 glusterfs-cli-3.7dev-0.1009.git8b987be.el7.centos.x86_64 glusterfs-3.7dev-0.1009.git8b987be.el7.centos.x86_64 glusterfs-server-3.7dev-0.1009.git8b987be.el7.centos.x86_64 glusterfs-fuse-3.7dev-0.1009.git8b987be.el7.centos.x86_64 glusterfs-libs-3.7dev-0.1009.git8b987be.el7.centos.x86_64 Steps to Reproduce: ================== 1.have a multinode gluster 2.create a dist-rep volume 3.attach a tier with replica as 10 and one brick Actual results: ================= glusterd crashes Expected results: =============== proper error msg should be thrown, if replica or bricks count are not correct
sosreports rhsqe-repo sosreports]# /home/repo/sosreports/1215122
REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#2) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#3) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/10428 (tiering/cli: Check replica count and bricks are proper or not) posted (#4) for review on master by mohammed rafi kc (rkavunga)
This change should not be in "ON_QA", the patch posted for this bug is only available in the master branch and not in a release yet. Moving back to MODIFIED until there is an beta release for the next GlusterFS version.
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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