Bug 765396 (GLUSTER-3664) - glusterd crashed when trying to mount a tcp,rdma volume via rdma transport
Summary: glusterd crashed when trying to mount a tcp,rdma volume via rdma transport
Keywords:
Status: CLOSED EOL
Alias: GLUSTER-3664
Product: GlusterFS
Classification: Community
Component: rdma
Version: pre-release
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 849124 858449
TreeView+ depends on / blocked
 
Reported: 2011-09-29 09:25 UTC by M S Vishwanath Bhat
Modified: 2016-06-01 01:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 849124 (view as bug list)
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
glusterd log file (27.08 KB, text/plain)
2011-09-29 06:25 UTC, M S Vishwanath Bhat
no flags Details

Description M S Vishwanath Bhat 2011-09-29 09:25:36 UTC
Created a volume with tcp,rdma transport type. Now I can mount this volume via tcp transport but when I tried to mount the same volume via rdma transport glusterd crahsed. Core is generated with following backtrace.

Loaded symbols for /usr/lib64/libmthca-rdmav2.so
Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libnss_files.so.2
Reading symbols from /lib64/libnss_dns.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libnss_dns.so.2
Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libresolv.so.2
Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libgcc_s.so.1

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff9f1fc000
Core was generated by `glusterd'.
Program terminated with signal 11, Segmentation fault.
#0  0x00002aaaab01d592 in rdma_decode_msg (peer=0x7901708, post=0x74cd7e0, readch=0x43b3f050, bytes_in_post=164) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:2804
2804                    memcpy (post->ctx.vector[0].iov_base, ptr,
(gdb) bt
#0  0x00002aaaab01d592 in rdma_decode_msg (peer=0x7901708, post=0x74cd7e0, readch=0x43b3f050, bytes_in_post=164) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:2804
#1  0x00002aaaab01d6d4 in rdma_decode_header (peer=0x7901708, post=0x74cd7e0, readch=0x43b3f050, bytes_in_post=164) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:2844
#2  0x00002aaaab01e4f6 in rdma_process_recv (peer=0x7901708, wc=0x43b3f0d0) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:3215
#3  0x00002aaaab01e93e in rdma_recv_completion_proc (data=0x5ea7420) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:3347
#4  0x000000328420673d in start_thread () from /lib64/libpthread.so.0
#5  0x0000003283ad40cd in clone () from /lib64/libc.so.6
(gdb) f 0
#0  0x00002aaaab01d592 in rdma_decode_msg (peer=0x7901708, post=0x74cd7e0, readch=0x43b3f050, bytes_in_post=164) at ../../../../../rpc/rpc-transport/rdma/src/rdma.c:2804
2804                    memcpy (post->ctx.vector[0].iov_base, ptr,
(gdb) 


I will upload the glusterd log file. I have archived the core file since it's too big to upload. (201MB)

Comment 1 Raghavendra G 2011-09-30 06:35:57 UTC
f78c8253d7fb7576 is causing some memory corruption.

Comment 2 Amar Tumballi 2012-02-27 10:35:50 UTC
This is the priority for immediate future (before 3.3.0 GA release). Will bump the priority up once we take RDMA related tasks.

Comment 3 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.


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