search for: dht_layout_search

Hi, I see a lot of the following messages in the logs: [2018-02-04 03:22:01.544446] I [glusterfsd-mgmt.c:1821:mgmt_getspec_cbk] 0-glusterfs: No change in volfile,continuing [2018-02-04 07:41:16.189349] W [MSGID: 109011] [dht-layout.c:186:dht_layout_search] 48-gv0-dht: no subvolume for hash (value) = 122440868 [2018-02-04 07:41:16.244261] W [fuse-bridge.c:2398:fuse_writev_cbk] 0-glusterfs-fuse: 3615890: WRITE => -1 gfid=c73ca10f-e83e-42a9-9b0a-1de4e12c6798 fd=0x7ffa3802a5f0 (?????? ?????/??????) [2018-02-04 07:41:16.254503] W [fuse-bridge.c:1377:f...

...edhat.com> wrote: > Hi, > > > I see a lot of the following messages in the logs: > [2018-02-04 03:22:01.544446] I [glusterfsd-mgmt.c:1821:mgmt_getspec_cbk] > 0-glusterfs: No change in volfile,continuing > [2018-02-04 07:41:16.189349] W [MSGID: 109011] > [dht-layout.c:186:dht_layout_search] 48-gv0-dht: no subvolume for hash > (value) = 122440868 > [2018-02-04 07:41:16.244261] W [fuse-bridge.c:2398:fuse_writev_cbk] > 0-glusterfs-fuse: 3615890: WRITE => -1 gfid=c73ca10f-e83e-42a9-9b0a-1de4e12c6798 > fd=0x7ffa3802a5f0 (?????? ?????/??????) > [2018-02-04 07:41:16.254503...

...i, >> >> >> I see a lot of the following messages in the logs: >> [2018-02-04 03:22:01.544446] I [glusterfsd-mgmt.c:1821:mgmt_getspec_cbk] >> 0-glusterfs: No change in volfile,continuing >> [2018-02-04 07:41:16.189349] W [MSGID: 109011] >> [dht-layout.c:186:dht_layout_search] 48-gv0-dht: no subvolume for hash >> (value) = 122440868 >> [2018-02-04 07:41:16.244261] W [fuse-bridge.c:2398:fuse_writev_cbk] >> 0-glusterfs-fuse: 3615890: WRITE => -1 gfid=c73ca10f-e83e-42a9-9b0a-1de4e12c6798 >> fd=0x7ffa3802a5f0 (?????? ?????/??????) >> [2018-0...

...>>> I see a lot of the following messages in the logs: >>> [2018-02-04 03:22:01.544446] I [glusterfsd-mgmt.c:1821:mgmt_getspec_cbk] >>> 0-glusterfs: No change in volfile,continuing >>> [2018-02-04 07:41:16.189349] W [MSGID: 109011] >>> [dht-layout.c:186:dht_layout_search] 48-gv0-dht: no subvolume for hash >>> (value) = 122440868 >>> [2018-02-04 07:41:16.244261] W [fuse-bridge.c:2398:fuse_writev_cbk] >>> 0-glusterfs-fuse: 3615890: WRITE => -1 gfid=c73ca10f-e83e-42a9-9b0a-1de4e12c6798 >>> fd=0x7ffa3802a5f0 (?????? ?????/??????)...

...name, Client A worked without problems. It seemed that there were some problems with special bricks in special clients. But all the bricks were online. I saw this in the logs in the GlusterFS client after creating directory failure: [2017-11-06 11:55:18.420610] W [MSGID: 109011] [dht-layout.c:186:dht_layout_search] 0-data-dht: no subvolume for hash (value) = 4148753024 [2017-11-06 11:55:18.457744] W [fuse-bridge.c:521:fuse_entry_cbk] 0-glusterfs-fuse: 488: MKDIR() /xxx => -1 (Input/output error) The message "W [MSGID: 109011] [dht-layout.c:186:dht_layout_search] 0-data-dht: no subvolume for hash (val...

...heal_completion_cbk] 0-adata-replicate-8: background data missing-entry gfid self-heal failed on /files/random-file.dat [2013-02-25 19:56:20.623378] I [dht-layout.c:593:dht_layout_normalize] 0-adata-dht: found anomalies in /files. holes=1 overlaps=0 [2013-02-25 19:56:20.623399] W [dht-layout.c:186:dht_layout_search] 0-adata-dht: no subvolume for hash (value) = 2967408968 [2013-02-25 19:56:20.623404] W [dht-selfheal.c:882:dht_selfheal_directory] 0-adata-dht: 1 subvolumes have unrecoverable errors [2013-02-25 19:56:20.623413] E [dht-common.c:1372:dht_lookup] 0-adata-dht: Failed to get hashed subvol for /files/r...

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:

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)