Displaying 4 results from an estimated 4 matches for "acfreeman".
2017 Nov 06
1
回复： glusterfs segmentation fault in rdma mode
...dht: no subvolume for hash (value) = 4148753024" repeated 3 times between [2017-11-06 11:55:18.420610] and [2017-11-06 11:55:18.457731]
------------------ ???? ------------------
???: "Ben&nbsp;Turner";<bturner at redhat.com>;
????: 2017?11?5?(???) ??3:00
???: "acfreeman"<21291285 at qq.com>;
??: "gluster-users"<gluster-users at gluster.org>;
??: Re: [Gluster-users] glusterfs segmentation fault in rdma mode
This looks like there could be some some problem requesting / leaking / whatever memory but without looking at the core its tough...
2017 Nov 04
0
glusterfs segmentation fault in rdma mode
This looks like there could be some some problem requesting / leaking / whatever memory but without looking at the core its tought to tell for sure. Note:
/usr/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0x78)[0x7f95bc54e618]
Can you open up a bugzilla and get us the core file to review?
-b
----- Original Message -----
> From: "???" <21291285 at qq.com>
> To:
2017 Nov 04
2
glusterfs segmentation fault in rdma mode
Hi, All,
I used Infiniband to connect all GlusterFS nodes and the clients. Previously I run IP over IB and everything was OK. Now I used rdma transport mode instead. And then I ran the traffic. After I while, the glusterfs process exited because of segmentation fault.
Here were the messages when I saw segmentation fault:
pending frames:
frame : type(0) op(0)
frame : type(0) op(0)
2017 Nov 05
0
回复： glusterfs segmentation fault in rdma mode
Hi? If there was only one client, there were not any problems even the traffic was very heavy. But if I used several clients to write the same volume, then I could see the segmentation fault. I used gdb to debug, but the performance was much lower than the previous test results, and we couldn't see the errors. We thought that the problem only occurred when multiple clients wrote the same