Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
On 05/09/2015 04:23 PM, Kotresh Hiremath Ravishankar wrote: > Hi, > > There are few regression failures with changelog translator init being failed > and a core is generated > as explained below. > > 1. Why changelog translator init failed? > > In snapshot test cases, virtual multiple peers are setup in single node, > which causes 'Address already in use' and 'port already in use' error. > Hence > changelog translator failed. > > 2. Even if changelog translator failed it should not core why is the core? > >Well, the stack trace in regression run didn't help much. >I induced the error manually in local system and could trace in gdb >and is happening as below. > >There is some memory corruption in cleanup_and_exit path when translators > are failed. >I suppose this could happen for any translator init failed and not only > specific to >changelog. Could some look into this? > > #0 0x76cb67e0 in pthread_spin_lock () from /lib64/libpthread.so.0 > #1 0x77b70db5 in __gf_free (free_ptr=0x7fffe4031700) at > mem-pool.c:303 > #2 0x77b7120c in mem_put (ptr=0x7fffe403171c) at mem-pool.c:570 > #3 0x77b43fb4 in log_buf_destroy (buf=buf@entry=0x7fffe403171c) at > logging.c:357 > #4 0x77b47001 in gf_log_flush_list (copy=copy@entry=0x7fffeb80aa50, > ctx=ctx@entry=0x614010) at logging.c:1711 > #5 0x77b4720d in gf_log_flush_extra_msgs (new=0, ctx=0x614010) at > logging.c:1777 > #6 gf_log_set_log_buf_size (buf_size=buf_size@entry=0) at logging.c:270 > #7 0x77b47267 in gf_log_disable_suppression_before_exit > (ctx=0x614010) at logging.c:437 > #8 0x004080ec in cleanup_and_exit (signum=signum@entry=0) at > glusterfsd.c:1217 > #9 0x00408a16 in glusterfs_process_volfp (ctx=ctx@entry=0x614010, > fp=fp@entry=0x7fffe40014f0) at glusterfsd.c:2183 > #10 0x0040ccf7 in mgmt_getspec_cbk (req=, > iov=, count=, myframe=0x7fffe4000fa4) at > glusterfsd-mgmt.c:1560 > #11 0x77915c70 in rpc_clnt_handle_reply (clnt=clnt@entry=0x66d280, > pollin=pollin@entry=0x7fffe4002540) at rpc-clnt.c:766 > #12 0x77915ee4 in rpc_clnt_notify (trans=, > mydata=0x66d2b0, event=, data=0x7fffe4002540) at rpc-clnt.c:894 > #13 0x779121f3 in rpc_transport_notify (this=this@entry=0x66d6f0, > event=event@entry=RPC_TRANSPORT_MSG_RECEIVED, data=data@entry=0x7fffe4002540) > at rpc-transport.c:543 > #14 0x7fffed2ca1f4 in socket_event_poll_in (this=this@entry=0x66d6f0) at > socket.c:2290 > #15 0x7fffed2ccfb4 in socket_event_handler (fd=fd@entry=8, > idx=idx@entry=1, data=0x66d6f0, poll_in=1, poll_out=0, poll_err=0) at > socket.c:2403 > #16 0x77b9aaba in event_dispatch_epoll_handler (event=0x7fffeb80ae90, > event_pool=0x632c80) at event-epoll.c:572 > #17 event_dispatch_epoll_worker (data=0x66e8b0) at event-epoll.c:674 > #18 0x76cb1ee5 in start_thread () from /lib64/libpthread.so.0 > #19 0x765f8b8d in clone () from /lib64/libc.so.6 Probably another candidate for http://review.gluster.org/#/c/10417/ to go in? ~Atin > > Thanks and Regards, > Kotresh H R > > ----- Original Message - >> From: "Kotresh Hiremath Ravishankar" >> To: "Vijay Bellur" >> Cc: "Gluster Devel" >> Sent: Saturday, May 9, 2015 1:06:07 PM >> Subject: Re: [Gluster-devel] regression: brick crashed because of changelog >> xlator init failure >> >> It is crashing in libgcc!!! >> >> Program terminated with signal 11, Segmentation fault. >> #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 >> Missing separate debuginfos, use: debuginfo-install >> glibc-2.12-1.149.el6_6.7.x86_64 keyutils-libs-1.4-5.el6.x86_64 >> krb5-libs-1.10.3-37.el6_6.x86_64 libcom_err-1.41.12-21.el6.x86_64 >> libgcc-4.4.7-11.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 >> openssl-1.0.1e-30.el6.8.x86_64 zlib-1.2.3-29.el6.x86_64 >> (gdb) bt >> #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 >> #1 0x7ffa2119 in _Unwind_Backtrace () from ./lib64/libgcc_s.so.1 >> #2 0x7ff56170b8f6 in backtrace () from ./lib64/libc.so.6 >> #3 0x7ff562826544 in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT, >> stacksize=200) >> at >> >> /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/logging.c:1097 >> #4 0x7ff562845b82 in gf_print_trace (signum=11, ctx=0xabc010) >> at >> >> /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/common-utils.c:618 >> #5 0x00409646 in glusterfsd_print_trace
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
Hi, There are few regression failures with changelog translator init being failed and a core is generated as explained below. 1. Why changelog translator init failed? In snapshot test cases, virtual multiple peers are setup in single node, which causes 'Address already in use' and 'port already in use' error. Hence changelog translator failed. 2. Even if changelog translator failed it should not core why is the core? Well, the stack trace in regression run didn't help much. I induced the error manually in local system and could trace in gdb and is happening as below. There is some memory corruption in cleanup_and_exit path when translators are failed. I suppose this could happen for any translator init failed and not only specific to changelog. Could some look into this? #0 0x76cb67e0 in pthread_spin_lock () from /lib64/libpthread.so.0 #1 0x77b70db5 in __gf_free (free_ptr=0x7fffe4031700) at mem-pool.c:303 #2 0x77b7120c in mem_put (ptr=0x7fffe403171c) at mem-pool.c:570 #3 0x77b43fb4 in log_buf_destroy (buf=buf@entry=0x7fffe403171c) at logging.c:357 #4 0x77b47001 in gf_log_flush_list (copy=copy@entry=0x7fffeb80aa50, ctx=ctx@entry=0x614010) at logging.c:1711 #5 0x77b4720d in gf_log_flush_extra_msgs (new=0, ctx=0x614010) at logging.c:1777 #6 gf_log_set_log_buf_size (buf_size=buf_size@entry=0) at logging.c:270 #7 0x77b47267 in gf_log_disable_suppression_before_exit (ctx=0x614010) at logging.c:437 #8 0x004080ec in cleanup_and_exit (signum=signum@entry=0) at glusterfsd.c:1217 #9 0x00408a16 in glusterfs_process_volfp (ctx=ctx@entry=0x614010, fp=fp@entry=0x7fffe40014f0) at glusterfsd.c:2183 #10 0x0040ccf7 in mgmt_getspec_cbk (req=, iov=, count=, myframe=0x7fffe4000fa4) at glusterfsd-mgmt.c:1560 #11 0x77915c70 in rpc_clnt_handle_reply (clnt=clnt@entry=0x66d280, pollin=pollin@entry=0x7fffe4002540) at rpc-clnt.c:766 #12 0x77915ee4 in rpc_clnt_notify (trans=, mydata=0x66d2b0, event=, data=0x7fffe4002540) at rpc-clnt.c:894 #13 0x779121f3 in rpc_transport_notify (this=this@entry=0x66d6f0, event=event@entry=RPC_TRANSPORT_MSG_RECEIVED, data=data@entry=0x7fffe4002540) at rpc-transport.c:543 #14 0x7fffed2ca1f4 in socket_event_poll_in (this=this@entry=0x66d6f0) at socket.c:2290 #15 0x7fffed2ccfb4 in socket_event_handler (fd=fd@entry=8, idx=idx@entry=1, data=0x66d6f0, poll_in=1, poll_out=0, poll_err=0) at socket.c:2403 #16 0x77b9aaba in event_dispatch_epoll_handler (event=0x7fffeb80ae90, event_pool=0x632c80) at event-epoll.c:572 #17 event_dispatch_epoll_worker (data=0x66e8b0) at event-epoll.c:674 #18 0x76cb1ee5 in start_thread () from /lib64/libpthread.so.0 #19 0x765f8b8d in clone () from /lib64/libc.so.6 Thanks and Regards, Kotresh H R - Original Message - > From: "Kotresh Hiremath Ravishankar" > To: "Vijay Bellur" > Cc: "Gluster Devel" > Sent: Saturday, May 9, 2015 1:06:07 PM > Subject: Re: [Gluster-devel] regression: brick crashed because of changelog > xlator init failure > > It is crashing in libgcc!!! > > Program terminated with signal 11, Segmentation fault. > #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 > Missing separate debuginfos, use: debuginfo-install > glibc-2.12-1.149.el6_6.7.x86_64 keyutils-libs-1.4-5.el6.x86_64 > krb5-libs-1.10.3-37.el6_6.x86_64 libcom_err-1.41.12-21.el6.x86_64 > libgcc-4.4.7-11.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 > openssl-1.0.1e-30.el6.8.x86_64 zlib-1.2.3-29.el6.x86_64 > (gdb) bt > #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 > #1 0x7ffa2119 in _Unwind_Backtrace () from ./lib64/libgcc_s.so.1 > #2 0x7ff56170b8f6 in backtrace () from ./lib64/libc.so.6 > #3 0x7ff562826544 in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT, > stacksize=200) > at > > /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/logging.c:1097 > #4 0x7ff562845b82 in gf_print_trace (signum=11, ctx=0xabc010) > at > > /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/common-utils.c:618 > #5 0x00409646 in glusterfsd_print_trace (signum=11) at > /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/glusterfsd/src/glusterfsd.c:2007 > #6 > #7 0x7ff554484fa9 in ?? () > #8 0x7ff561d8b9d1 in start_thread () from ./lib64/libpthread.so.0 > #9 0x7ff5616f58fd in clone () from ./lib64/libc.so.6 > > > Thanks and Regards, > Kotresh H R > > - Original Message - > > From: "Vijay Bellur" > > To: "Kotresh Hiremath Ravishankar" , "Pranith Kumar > > Karampuri" > > Cc: "Gluster Devel" > > Sent: Saturday,
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
It is crashing in libgcc!!! Program terminated with signal 11, Segmentation fault. #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.149.el6_6.7.x86_64 keyutils-libs-1.4-5.el6.x86_64 krb5-libs-1.10.3-37.el6_6.x86_64 libcom_err-1.41.12-21.el6.x86_64 libgcc-4.4.7-11.el6.x86_64 libselinux-2.0.94-5.8.el6.x86_64 openssl-1.0.1e-30.el6.8.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt #0 0x7ffa1867 in ?? () from ./lib64/libgcc_s.so.1 #1 0x7ffa2119 in _Unwind_Backtrace () from ./lib64/libgcc_s.so.1 #2 0x7ff56170b8f6 in backtrace () from ./lib64/libc.so.6 #3 0x7ff562826544 in _gf_msg_backtrace_nomem (level=GF_LOG_ALERT, stacksize=200) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/logging.c:1097 #4 0x7ff562845b82 in gf_print_trace (signum=11, ctx=0xabc010) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/common-utils.c:618 #5 0x00409646 in glusterfsd_print_trace (signum=11) at /home/jenkins/root/workspace/rackspace-regression-2GB-triggered/glusterfsd/src/glusterfsd.c:2007 #6 #7 0x7ff554484fa9 in ?? () #8 0x7ff561d8b9d1 in start_thread () from ./lib64/libpthread.so.0 #9 0x7ff5616f58fd in clone () from ./lib64/libc.so.6 Thanks and Regards, Kotresh H R - Original Message - > From: "Vijay Bellur" > To: "Kotresh Hiremath Ravishankar" , "Pranith Kumar > Karampuri" > Cc: "Gluster Devel" > Sent: Saturday, May 9, 2015 12:52:33 PM > Subject: Re: [Gluster-devel] regression: brick crashed because of changelog > xlator init failure > > On 05/09/2015 12:49 PM, Kotresh Hiremath Ravishankar wrote: > > If you observe the logs below. Socket binding failed because of Address and > > port already in use ERROR. > > Because of that changelog failed to initiate rpc server, hence failed. > > Not sure why socket binding failed in this machine. > > > > [2015-05-08 21:34:47.747059] E [socket.c:823:__socket_server_bind] > > 0-socket.patchy-changelog: binding to failed: Address already in use > > [2015-05-08 21:34:47.747078] E [socket.c:826:__socket_server_bind] > > 0-socket.patchy-changelog: Port is already in use > > [2015-05-08 21:34:47.747096] W [rpcsvc.c:1602:rpcsvc_transport_create] > > 0-rpc-service: listening on transport failed > > [2015-05-08 21:34:47.747197] I [mem-pool.c:587:mem_pool_destroy] > > 0-patchy-changelog: size=116 max=0 total=0 > > [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] > > 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, > > review your volfile again > > [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] > > 0-patchy-changelog: initializing translator failed > > [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate] > > 0-graph: init failed > > [2015-05-08 21:34:47.749020] I > > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread > > with index 2 > > Irrespective of a socket bind failing, we should not crash. any ideas > why glusterfsd crashed? > > -Vijay > > > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
On 05/09/2015 12:49 PM, Kotresh Hiremath Ravishankar wrote: If you observe the logs below. Socket binding failed because of Address and port already in use ERROR. Because of that changelog failed to initiate rpc server, hence failed. Not sure why socket binding failed in this machine. [2015-05-08 21:34:47.747059] E [socket.c:823:__socket_server_bind] 0-socket.patchy-changelog: binding to failed: Address already in use [2015-05-08 21:34:47.747078] E [socket.c:826:__socket_server_bind] 0-socket.patchy-changelog: Port is already in use [2015-05-08 21:34:47.747096] W [rpcsvc.c:1602:rpcsvc_transport_create] 0-rpc-service: listening on transport failed [2015-05-08 21:34:47.747197] I [mem-pool.c:587:mem_pool_destroy] 0-patchy-changelog: size=116 max=0 total=0 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, review your volfile again [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] 0-patchy-changelog: initializing translator failed [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed [2015-05-08 21:34:47.749020] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 Irrespective of a socket bind failing, we should not crash. any ideas why glusterfsd crashed? -Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
If you observe the logs below. Socket binding failed because of Address and port already in use ERROR. Because of that changelog failed to initiate rpc server, hence failed. Not sure why socket binding failed in this machine. [2015-05-08 21:34:47.747059] E [socket.c:823:__socket_server_bind] 0-socket.patchy-changelog: binding to failed: Address already in use [2015-05-08 21:34:47.747078] E [socket.c:826:__socket_server_bind] 0-socket.patchy-changelog: Port is already in use [2015-05-08 21:34:47.747096] W [rpcsvc.c:1602:rpcsvc_transport_create] 0-rpc-service: listening on transport failed [2015-05-08 21:34:47.747197] I [mem-pool.c:587:mem_pool_destroy] 0-patchy-changelog: size=116 max=0 total=0 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, review your volfile again [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] 0-patchy-changelog: initializing translator failed [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed [2015-05-08 21:34:47.749020] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 pending frames: frame : type(0) op(0) patchset: git://git.gluster.com/glusterfs.git signal received: 11 time of crash: 2015-05-08 21:34:47 configuration details: argp 1 1679,6 60% Thanks and Regards, Kotresh H R - Original Message - > From: "Kotresh Hiremath Ravishankar" > To: "Pranith Kumar Karampuri" > Cc: "Gluster Devel" > Sent: Saturday, May 9, 2015 11:04:10 AM > Subject: Re: [Gluster-devel] regression: brick crashed because of changelog > xlator init failure > > Hi Pranith, > > I think you pasted the wrong patch link. > Could you share the correct patch link? > > Thanks and Regards, > Kotresh H R > > - Original Message - > > From: "Pranith Kumar Karampuri" > > To: "Kotresh Hiremath Ravishankar" , "Aravinda > > Vishwanathapura Krishna Murthy" > > > > Cc: "Gluster Devel" > > Sent: Saturday, May 9, 2015 3:26:24 AM > > Subject: regression: brick crashed because of changelog xlator init failure > > > > hi Kotresh/Aravinda, > > Do you guys know anything about following core which comes because > > of changelog xlator init failure? It just failed regression on one of my > > patches: http://review.gluster.org/#/c/10688 > > > > 24 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] > > 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, > > review your volfile again > > 23 [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] > > 0-patchy-changelog: initializing translator failed > > 22 [2015-05-08 21:34:47.750497] E > > [graph.c:661:glusterfs_graph_activate] 0-graph: init failed > > 21 [2015-05-08 21:34:47.749020] I > > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread > > with index 2 > > 20 pending frames: > > 19 frame : type(0) op(0) > > 18 patchset: git://git.gluster.com/glusterfs.git > > 17 signal received: 11 > > 16 time of crash: > > 15 2015-05-08 21:34:47 > > 14 configuration details: > > 13 argp 1 > > 12 backtrace 1 > > 11 dlfcn 1 > > 10 libpthread 1 > >9 llistxattr 1 > >8 setfsid 1 > >7 spinlock 1 > >6 epoll.h 1 > >5 xattr.h 1 > >4 st_atim.tv_nsec 1 > >3 package-string: glusterfs 3.7.0beta1 > >2 pending frames: > >1 frame : type(0) op(0) > >0 patchset: git://git.gluster.com/glusterfs.git > > > > Pranith > > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
Hi Pranith, I think you pasted the wrong patch link. Could you share the correct patch link? Thanks and Regards, Kotresh H R - Original Message - > From: "Pranith Kumar Karampuri" > To: "Kotresh Hiremath Ravishankar" , "Aravinda > Vishwanathapura Krishna Murthy" > > Cc: "Gluster Devel" > Sent: Saturday, May 9, 2015 3:26:24 AM > Subject: regression: brick crashed because of changelog xlator init failure > > hi Kotresh/Aravinda, > Do you guys know anything about following core which comes because > of changelog xlator init failure? It just failed regression on one of my > patches: http://review.gluster.org/#/c/10688 > > 24 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] > 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, > review your volfile again > 23 [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] > 0-patchy-changelog: initializing translator failed > 22 [2015-05-08 21:34:47.750497] E > [graph.c:661:glusterfs_graph_activate] 0-graph: init failed > 21 [2015-05-08 21:34:47.749020] I > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread > with index 2 > 20 pending frames: > 19 frame : type(0) op(0) > 18 patchset: git://git.gluster.com/glusterfs.git > 17 signal received: 11 > 16 time of crash: > 15 2015-05-08 21:34:47 > 14 configuration details: > 13 argp 1 > 12 backtrace 1 > 11 dlfcn 1 > 10 libpthread 1 >9 llistxattr 1 >8 setfsid 1 >7 spinlock 1 >6 epoll.h 1 >5 xattr.h 1 >4 st_atim.tv_nsec 1 >3 package-string: glusterfs 3.7.0beta1 >2 pending frames: >1 frame : type(0) op(0) >0 patchset: git://git.gluster.com/glusterfs.git > > Pranith > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] regression: brick crashed because of changelog xlator init failure
On 05/09/2015 03:26 AM, Pranith Kumar Karampuri wrote: hi Kotresh/Aravinda, Do you guys know anything about following core which comes because of changelog xlator init failure? It just failed regression on one of my patches: http://review.gluster.org/#/c/10688 Sorry wrong URL, this is the correct one: http://review.gluster.com/#/c/10693/ Pranith 24 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, review your volfile again 23 [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] 0-patchy-changelog: initializing translator failed 22 [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed 21 [2015-05-08 21:34:47.749020] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 20 pending frames: 19 frame : type(0) op(0) 18 patchset: git://git.gluster.com/glusterfs.git 17 signal received: 11 16 time of crash: 15 2015-05-08 21:34:47 14 configuration details: 13 argp 1 12 backtrace 1 11 dlfcn 1 10 libpthread 1 9 llistxattr 1 8 setfsid 1 7 spinlock 1 6 epoll.h 1 5 xattr.h 1 4 st_atim.tv_nsec 1 3 package-string: glusterfs 3.7.0beta1 2 pending frames: 1 frame : type(0) op(0) 0 patchset: git://git.gluster.com/glusterfs.git Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] regression: brick crashed because of changelog xlator init failure
hi Kotresh/Aravinda, Do you guys know anything about following core which comes because of changelog xlator init failure? It just failed regression on one of my patches: http://review.gluster.org/#/c/10688 24 [2015-05-08 21:34:47.750460] E [xlator.c:426:xlator_init] 0-patchy-changelog: Initialization of volume 'patchy-changelog' failed, review your volfile again 23 [2015-05-08 21:34:47.750485] E [graph.c:322:glusterfs_graph_init] 0-patchy-changelog: initializing translator failed 22 [2015-05-08 21:34:47.750497] E [graph.c:661:glusterfs_graph_activate] 0-graph: init failed 21 [2015-05-08 21:34:47.749020] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 20 pending frames: 19 frame : type(0) op(0) 18 patchset: git://git.gluster.com/glusterfs.git 17 signal received: 11 16 time of crash: 15 2015-05-08 21:34:47 14 configuration details: 13 argp 1 12 backtrace 1 11 dlfcn 1 10 libpthread 1 9 llistxattr 1 8 setfsid 1 7 spinlock 1 6 epoll.h 1 5 xattr.h 1 4 st_atim.tv_nsec 1 3 package-string: glusterfs 3.7.0beta1 2 pending frames: 1 frame : type(0) op(0) 0 patchset: git://git.gluster.com/glusterfs.git Pranith ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
