On 03/09/2016 04:58 PM, Niels de Vos wrote: > On Wed, Mar 09, 2016 at 10:27:58AM +0000, Martel, Michael H wrote: >> Greetings! >> >> I upgraded our gluster server and clients to 3.5.7 this morning. While checking on the status of the clients (gluster volume status moodledata clients) gluster stopped responding to requests. The clients were fine. >> >> I found this in the logfiles. Any thoughts ? Thanks! >> >> >> [2016-03-09 09:55:08.586354] I [glusterd-handler.c:3530:__glusterd_handle_status_volume] 0-management: Received status volume req for volu me moodledata >> pending frames: >> frame : type(0) op(0) >> >> patchset: git://git.gluster.com/glusterfs.git >> signal received: 11 >> time of crash: 2016-03-09 09:55:08configuration details: >> argp 1 >> backtrace 1 >> dlfcn 1 >> fdatasync 1 >> libpthread 1 >> llistxattr 1 >> setfsid 1 >> spinlock 1 >> epoll.h 1 >> xattr.h 1 >> st_atim.tv_nsec 1 >> package-string: glusterfs 3.5.7 >> /lib/x86_64-linux-gnu/libc.so.6(+0x321a0)[0x7f37b94da1a0] >> /lib/x86_64-linux-gnu/libc.so.6(+0x115afa)[0x7f37b95bdafa] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(glusterd_add_brick_detail_to_dict+0x9af)[0x7f37b640575f] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(glusterd_op_commit_perform+0x1be4)[0x7f37b63f6304] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(gd_commit_op_phase+0xa3)[0x7f37b6454ce3] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(gd_sync_task_begin+0x306)[0x7f37b6455966] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(glusterd_op_begin_synctask+0x3b)[0x7f37b6455abb] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(__glusterd_handle_status_volume+0x149)[0x7f37b63dc4a9] >> /usr/lib/x86_64-linux-gnu/glusterfs/3.5.7/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x3f)[0x7f37b63e5c5f] >> /usr/lib/x86_64-linux-gnu/libglusterfs.so.0(synctask_wrap+0x12)[0x7f37ba4d0e62] >> /lib/x86_64-linux-gnu/libc.so.6(+0x42cd0)[0x7f37b94eacd0] >> --------- > > This looks very much like a bug that was reported against 3.6. It seemed > to have happened with filesystems that Gluster does not know how to > handle. Could you file a bug against version 3.5.x, attach the above > stack trace as a file and repeat in the report what version you upgraded > from. Let us know the bug number and we'll look into fixing this. > > https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&component=glusterd&version=3.5.7 > > Most likely releted: https://bugzilla.redhat.com/show_bug.cgi?id=1173909 > It is highly appreciated if someone would like to send the backports of > patches for this bug. I could see that we have missed few backports for this function and thanks Niels for point that. I'd take this up to send the backports to both 3.5 & 3.6 (if required). ~Atin > > Thanks, > Niels > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
