search for: fuse_getattr_resume

...1046] [dht-common.c:1501:dht_lookup_dir_cbk] 0-gv01-dht: dict is null [2018-04-09 05:08:13.927301] W [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: 00000000-0000-0000-0000-000000000001: failed to resolve (Transport endpoint is not connected) [2018-04-09 05:08:13.927339] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-fuse: 2: GETATTR 1 (00000000-0000-0000-0000-000000000001) resolution failed [2018-04-09 05:08:13.931497] I [MSGID: 108006] [afr-common.c:5444:afr_local_init] 0-gv01-replicate-0: no subvolumes up [2018-04-09 05:08:13.931558] E [MSGID: 101046] [dht-common.c:1501:dht_lookup_dir_cbk] 0...

...501:dht_lookup_dir_cbk] 0-gv01-dht: dict is null > [2018-04-09 05:08:13.927301] W > [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: > 00000000-0000-0000-0000-000000000001: failed to resolve (Transport > endpoint is not connected) > [2018-04-09 05:08:13.927339] E [fuse-bridge.c:900:fuse_getattr_resume] > 0-glusterfs-fuse: 2: GETATTR 1 (00000000-0000-0000-0000-000000000001) > resolution failed > [2018-04-09 05:08:13.931497] I [MSGID: 108006] > [afr-common.c:5444:afr_local_init] 0-gv01-replicate-0: no subvolumes up > [2018-04-09 05:08:13.931558] E [MSGID: 101046] > [dht-common.c:...

...bk] 0-gv01-dht: dict is null > [2018-04-09 05:08:13.927301] W > [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: > 00000000-0000-0000-0000-000000000001: failed to resolve (Transport > endpoint is not connected) > [2018-04-09 05:08:13.927339] E [fuse-bridge.c:900:fuse_getattr_resume] > 0-glusterfs-fuse: 2: GETATTR 1 (00000000-0000-0000-0000-000000000001) > resolution failed > [2018-04-09 05:08:13.931497] I [MSGID: 108006] > [afr-common.c:5444:afr_local_init] 0-gv01-replicate-0: no subvolumes up > [2018-04-09 05:08:13.931558] E [MSGID: 101046]...

On Wed, Apr 11, 2018 at 4:35 AM, TomK <tomkcpr at mdevsys.com> wrote: > On 4/9/2018 2:45 AM, Alex K wrote: > Hey Alex, > > With two nodes, the setup works but both sides go down when one node is > missing. Still I set the below two params to none and that solved my issue: > > cluster.quorum-type: none > cluster.server-quorum-type: none > > yes this disables

...389171] E [fuse-bridge.c:4271:fuse_first_lookup] 0-fuse: first lookup on root failed (Transport endpoint is not connected) n.log:[2018-05-05 01:38:46.974945] E [MSGID: 101046] [dht-common.c:1501:dht_lookup_dir_cbk] 0-gv01-dht: dict is null n.log:[2018-05-05 01:38:46.975012] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-fuse: 2: GETATTR 1 (00000000-0000-0000-0000-000000000001) resolution failed n.log:[2018-05-05 01:38:47.010671] E [MSGID: 101046] [dht-common.c:1501:dht_lookup_dir_cbk] 0-gv01-dht: dict is null n.log:[2018-05-05 01:38:47.010731] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-f...

...er using "remove-brick start" as that will automatically rebalance data. Regards, Nithya On 5 February 2018 at 14:06, Nikita Yeryomin <nikyer at gmail.com> wrote: > Attached the log. There are some errors in it like > > [2018-02-04 18:50:41.112962] E [fuse-bridge.c:903:fuse_getattr_resume] > 0-glusterfs-fuse: 9613852: GETATTR 140712792330896 > (7d39d329-c0e0-4997-85e6-0e66e0436315) resolution failed > > But when it occurs it seems not affecting current file i/o operations. > I've already re-created the volume yesterday and I was not able to > reproduce the erro...

...will automatically rebalance data. > > > > Regards, > Nithya > > On 5 February 2018 at 14:06, Nikita Yeryomin <nikyer at gmail.com> wrote: > >> Attached the log. There are some errors in it like >> >> [2018-02-04 18:50:41.112962] E [fuse-bridge.c:903:fuse_getattr_resume] >> 0-glusterfs-fuse: 9613852: GETATTR 140712792330896 >> (7d39d329-c0e0-4997-85e6-0e66e0436315) resolution failed >> >> But when it occurs it seems not affecting current file i/o operations. >> I've already re-created the volume yesterday and I was not able to &gt...

...>> >> >> Regards, >> Nithya >> >> On 5 February 2018 at 14:06, Nikita Yeryomin <nikyer at gmail.com> wrote: >> >>> Attached the log. There are some errors in it like >>> >>> [2018-02-04 18:50:41.112962] E [fuse-bridge.c:903:fuse_getattr_resume] >>> 0-glusterfs-fuse: 9613852: GETATTR 140712792330896 >>> (7d39d329-c0e0-4997-85e6-0e66e0436315) resolution failed >>> >>> But when it occurs it seems not affecting current file i/o operations. >>> I've already re-created the volume yesterday and I...

...Regards, >>> Nithya >>> >>> On 5 February 2018 at 14:06, Nikita Yeryomin <nikyer at gmail.com> wrote: >>> >>>> Attached the log. There are some errors in it like >>>> >>>> [2018-02-04 18:50:41.112962] E [fuse-bridge.c:903:fuse_getattr_resume] >>>> 0-glusterfs-fuse: 9613852: GETATTR 140712792330896 >>>> (7d39d329-c0e0-4997-85e6-0e66e0436315) resolution failed >>>> >>>> But when it occurs it seems not affecting current file i/o operations. >>>> I've already re-created the vo...

...14029] [client-rpc-fops.c:4384:client3_3_writev] 2-scratch-client-0: failed to send the fop [2018-02-22 18:07:45.231486] W [MSGID: 103037] [rdma.c:3016:gf_rdma_submit_request] 2-rpc-transport/rdma: sending request to peer (172.17.2.254:24008) failed [2018-02-22 18:07:45.231501] E [fuse-bridge.c:796:fuse_getattr_resume] 0-glusterfs-fuse: 790393: GETATTR 47480857159808 (3a86afe5-7392-49a5-b60a-e0c93b050c01) resolution failed [2018-02-22 18:07:45.231494] W [MSGID: 103026] [rdma.c:2843:gf_rdma_writev] 2-scratch-client-1: rdma is not connected to peer (172.17.2.255:24008) [2018-02-22 18:07:45.231509] W [rpc-clnt.c:16...