Bug 795651 - gluster client crashed while mounting
Summary: gluster client crashed while mounting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: stat-prefetch
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-21 07:09 UTC by Shwetha Panduranga
Modified: 2013-07-24 17:45 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:45:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shwetha Panduranga 2012-02-21 07:09:02 UTC
Description of problem:
Program terminated with signal 6, Aborted.
#0  0x000000368d232905 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.25.el6_1.3.x86_64 libgcc-4.4.6-3.el6.x86_64
(gdb) bt
#0  0x000000368d232905 in raise () from /lib64/libc.so.6
#1  0x000000368d2340e5 in abort () from /lib64/libc.so.6
#2  0x000000368d22b9be in __assert_fail_base () from /lib64/libc.so.6
#3  0x000000368d22ba80 in __assert_fail () from /lib64/libc.so.6
#4  0x00007fae9db831be in gf_mem_set_acct_info (xl=0xe457a0, alloc_ptr=0x7fff24de63a0, size=4, type=92) at mem-pool.c:96
#5  0x00007fae9db8349f in __gf_calloc (nmemb=4, size=1, type=92) at mem-pool.c:151
#6  0x00007fae96f57cd0 in init (this=0xe457a0) at md-cache.c:1701
#7  0x00007fae9db502fe in __xlator_init (xl=0xe457a0) at xlator.c:365
#8  0x00007fae9db50428 in xlator_init (xl=0xe457a0) at xlator.c:388
#9  0x00007fae9db91893 in glusterfs_graph_init (graph=0xe392e0) at graph.c:300
#10 0x00007fae9db92039 in glusterfs_graph_activate (graph=0xe392e0, ctx=0xe16010) at graph.c:490
#11 0x00000000004078d2 in glusterfs_process_volfp (ctx=0xe16010, fp=0xe38e40) at glusterfsd.c:1485
#12 0x000000000040b7a4 in mgmt_getspec_cbk (req=0x7fae98d1d04c, iov=0x7fae98d1d08c, count=1, myframe=0x7fae9b7367bc) at glusterfsd-mgmt.c:1330
#13 0x00007fae9d92c7b4 in rpc_clnt_handle_reply (clnt=0xe35a80, pollin=0xe38940) at rpc-clnt.c:790
#14 0x00007fae9d92cb3b in rpc_clnt_notify (trans=0xe35da0, mydata=0xe35ab0, event=RPC_TRANSPORT_MSG_RECEIVED, data=0xe38940) at rpc-clnt.c:908
#15 0x00007fae9d928d18 in rpc_transport_notify (this=0xe35da0, event=RPC_TRANSPORT_MSG_RECEIVED, data=0xe38940) at rpc-transport.c:498
#16 0x00007fae98a95270 in socket_event_poll_in (this=0xe35da0) at socket.c:1686
#17 0x00007fae98a957f4 in socket_event_handler (fd=6, idx=0, data=0xe35da0, poll_in=1, poll_out=0, poll_err=0) at socket.c:1801
#18 0x00007fae9db828b8 in event_dispatch_epoll_handler (event_pool=0xe2ec20, events=0xe37b10, i=0) at event.c:794
#19 0x00007fae9db82adb in event_dispatch_epoll (event_pool=0xe2ec20) at event.c:856
#20 0x00007fae9db82e66 in event_dispatch (event_pool=0xe2ec20) at event.c:956
#21 0x0000000000407c6e in main (argc=4, argv=0x7fff24de6af8) at glusterfsd.c:1601
(gdb) f 4
#4  0x00007fae9db831be in gf_mem_set_acct_info (xl=0xe457a0, alloc_ptr=0x7fff24de63a0, size=4, type=92) at mem-pool.c:96
96	                GF_ASSERT (0);
(gdb) l
91	        if (!(xl->mem_acct.rec)) {
92	                GF_ASSERT (0);
93	        }
94	
95	        if (type > xl->mem_acct.num_types) {
96	                GF_ASSERT (0);
97	        }
98	
99	        LOCK(&xl->mem_acct.rec[type].lock);
100	        {


Version-Release number of selected component (if applicable):
mainline

How reproducible:
often

Comment 1 Anand Avati 2012-02-21 07:22:18 UTC
CHANGE: http://review.gluster.com/2778 (performance/md-cache: Add mem_acct_init) merged in master by Vijay Bellur (vijay)

Comment 2 Shwetha Panduranga 2012-02-21 07:28:07 UTC
Verified on mainline. Works fine.


Note You need to log in before you can comment on or make changes to this bug.