search for: 113020

Displaying 18 results from an estimated 18 matches for "113020".

Did you mean: 11020
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...icks/brick-brick2-gv2a2.log (the interested volume): [2018-01-16 15:14:37.809965] I [MSGID: 115029] [server-handshake.c:793:server_setvolume] 0-gv2a2-server: accepted client from ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 (version: 3.12.4) [2018-01-16 15:16:41.471751] E [MSGID: 113020] [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 failed [2018-01-16 15:16:41.471745] W [MSGID: 113096] [posix-handle.c:770:posix_handle_hard] 0-gv2a2-posix: link /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cf...
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...terested volume): > > [2018-01-16 15:14:37.809965] I [MSGID: 115029] > [server-handshake.c:793:server_setvolume] 0-gv2a2-server: accepted > client from > ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 (version: > 3.12.4) > [2018-01-16 15:16:41.471751] E [MSGID: 113020] > [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on > /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 failed > [2018-01-16 15:16:41.471745] W [MSGID: 113096] > [posix-handle.c:770:posix_handle_hard] 0-gv2a2-posix: link > /bricks/brick2/gv2a2/.shard/623...
2018 Jan 16
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...gt;> [2018-01-16 15:14:37.809965] I [MSGID: 115029] >> [server-handshake.c:793:server_setvolume] 0-gv2a2-server: accepted >> client from >> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 (version: >> 3.12.4) >> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 failed >> [2018-01-16 15:16:41.471745] W [MSGID: 113096] >> [posix-handle.c:770:posix_handle_hard] 0-gv2a2-posix: link >> /bricks/bri...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...2.log (the interested volume): > > [2018-01-16 15:14:37.809965] I [MSGID: 115029] [server-handshake.c:793:server_setvolume] > 0-gv2a2-server: accepted client from ovh-ov1-10302-2018/01/16-15: > 14:37:790306-gv2a2-client-0-0-0 (version: 3.12.4) > [2018-01-16 15:16:41.471751] E [MSGID: 113020] [posix.c:1485:posix_mknod] > 0-gv2a2-posix: setting gfid on /bricks/brick2/gv2a2/.shard/ > 62335cb9-c7b5-4735-a879-59cff93fe622.4 failed > [2018-01-16 15:16:41.471745] W [MSGID: 113096] [posix-handle.c:770:posix_handle_hard] > 0-gv2a2-posix: link /bricks/brick2/gv2a2/.shard/62335cb9-c7...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...I [MSGID: 115029] >>> [server-handshake.c:793:server_setvolume] 0-gv2a2-server: >>> accepted client from >>> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>> (version: 3.12.4) >>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>> failed >>> [2018-01-16 15:16:41.471745] W [MSGID: 113096] >>> [posix-handle.c:770:posix_handle_h...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...): >> >> [2018-01-16 15:14:37.809965] I [MSGID: 115029] >> [server-handshake.c:793:server_setvolume] 0-gv2a2-server: accepted >> client from ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >> (version: 3.12.4) >> [2018-01-16 15:16:41.471751] E [MSGID: 113020] [posix.c:1485:posix_mknod] >> 0-gv2a2-posix: setting gfid on /bricks/brick2/gv2a2/.shard/62 >> 335cb9-c7b5-4735-a879-59cff93fe622.4 failed >> [2018-01-16 15:16:41.471745] W [MSGID: 113096] >> [posix-handle.c:770:posix_handle_hard] 0-gv2a2-posix: link >> /bricks/brick2...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...[server-handshake.c:793:server_setvolume] 0-gv2a2-server: >>>> accepted client from >>>> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>>> (version: 3.12.4) >>>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >>>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>>> failed >>>> [2018-01-16 15:16:41.471745] W [MSGID: 113096] >>>>...
2018 Jan 17
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...shake.c:793:server_setvolume] 0-gv2a2-server: >>>>> accepted client from >>>>> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>>>> (version: 3.12.4) >>>>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>>>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >>>>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>>>> failed >>>>> [2018-01-16 15:16:41.471745] W [MSGID: 113096] &gt...
2018 Jan 16
1
Problem with Gluster 3.12.4, VM and sharding
Also to help isolate the component, could you answer these: 1. on a different volume with shard not enabled, do you see this issue? 2. on a plain 3-way replicated volume (no arbiter), do you see this issue? On Tue, Jan 16, 2018 at 4:03 PM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > Please share the volume-info output and the logs under /var/log/glusterfs/ > from all your
2018 Jan 18
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...er_setvolume] 0-gv2a2-server: >>>>>> accepted client from >>>>>> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>>>>> (version: 3.12.4) >>>>>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>>>>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >>>>>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>>>>> failed >>>>>> [2018-01-16 15:16:41.471745] W [MS...
2018 Jan 18
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...> [2018-01-16 15:14:37.809965] I [MSGID: 115029] >>> [server-handshake.c:793:server_setvolume] 0-gv2a2-server: accepted >>> client from ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>> (version: 3.12.4) >>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting gfid on >>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>> failed >>> [2018-01-16 15:16:41.471745] W [MSGID: 113096] >>> [posix-handle.c:770:posix_handle_hard] 0-gv2a2-posix:...
2018 Jan 19
1
[Possibile SPAM] Re: Problem with Gluster 3.12.4, VM and sharding
...t;>> 0-gv2a2-server: accepted client from >>>>>>> ovh-ov1-10302-2018/01/16-15:14:37:790306-gv2a2-client-0-0-0 >>>>>>> (version: 3.12.4) >>>>>>> [2018-01-16 15:16:41.471751] E [MSGID: 113020] >>>>>>> [posix.c:1485:posix_mknod] 0-gv2a2-posix: setting >>>>>>> gfid on >>>>>>> /bricks/brick2/gv2a2/.shard/62335cb9-c7b5-4735-a879-59cff93fe622.4 >>>>>>> failed &g...
2011 Feb 26
0
[LLVMdev] X86 LowerVECTOR_SHUFFLE Question
...r x86 has this code: > > if (X86::isUNPCKLMask(SVOp)) > getTargetShuffleNode(getUNPCKLOpcode(VT) dl, VT, V1, V2, DAG); > > why would this not be: > > if (X86::isUNPCKLMask(SVOp)) > return SVOp; Ok, I discovered that Bruno did this in revisions 112934, 112942 and 113020 but the logs don't really make clear why. I did figure out that I needed new SDNode defs for VUNPCKLPSY and VUNPCKLPDY and corresponding patterns. Once I added them everything started working. I found this all very confusing because it appears there are now two ways to match certain shuffle...
2011 Feb 25
2
[LLVMdev] X86 LowerVECTOR_SHUFFLE Question
In ToT, LowerVECTOR_SHUFFLE for x86 has this code: if (X86::isUNPCKLMask(SVOp)) getTargetShuffleNode(getUNPCKLOpcode(VT) dl, VT, V1, V2, DAG); why would this not be: if (X86::isUNPCKLMask(SVOp)) return SVOp; I'm trying to add support for VUNPCKL and am getting into trouble because the existing code ends up creating: VUNPCKLPS load load which is badness come selection
2017 Jun 28
2
setting gfid on .trashcan/... failed - total outage
...in 3.8 resp. 3.10... ? unfortunately i did not found corresponding informations in the release notes... best regards Dietmar the partial outage started as shown below, the very first entries occurred in the brick-logs : gl-master-04, brick1-mvol1.log : [2017-06-23 16:35:11.373471] E [MSGID: 113020] [posix.c:2839:posix_create] 0-mvol1-posix: setting gfid on /brick1/mvol1/.trashcan//2290/uploads/170221_Sendung_Lieberum_01_AT.mp4_2017-06-23_163511 failed [2017-06-23 16:35:11.392540] E [posix.c:3188:_fill_writev_xdata] (-->/usr/lib/x86_64-linux-gnu/glusterfs/3.7.18/xlator/features/trash.s...
2017 Jun 29
0
setting gfid on .trashcan/... failed - total outage
...ponding informations in the release? > notes... > > best regards > Dietmar > > > the partial outage started as shown below, the very first entries? > occurred in the brick-logs : > > gl-master-04, brick1-mvol1.log : > > [2017-06-23 16:35:11.373471] E [MSGID: 113020]? > [posix.c:2839:posix_create] 0-mvol1-posix: setting gfid on? > /brick1/mvol1/.trashcan//2290/uploads/170221_Sendung_Lieberum_01_AT.mp4_2017-06-23_163511? > failed > [2017-06-23 16:35:11.392540] E [posix.c:3188:_fill_writev_xdata]? > (-->/usr/lib/x86_64-linux- > gnu/glusterfs...
2017 Jun 29
1
setting gfid on .trashcan/... failed - total outage
...gt; notes... >> >> best regards >> Dietmar >> >> >> the partial outage started as shown below, the very first entries >> occurred in the brick-logs : >> >> gl-master-04, brick1-mvol1.log : >> >> [2017-06-23 16:35:11.373471] E [MSGID: 113020] >> [posix.c:2839:posix_create] 0-mvol1-posix: setting gfid on >> /brick1/mvol1/.trashcan//2290/uploads/170221_Sendung_Lieberum_01_AT.mp4_2017-06-23_163511 >> failed >> [2017-06-23 16:35:11.392540] E [posix.c:3188:_fill_writev_xdata] >> (-->/usr/lib/x86_64-linux- &g...
2011 Feb 26
2
[LLVMdev] X86 LowerVECTOR_SHUFFLE Question
...86::isUNPCKLMask(SVOp)) >> getTargetShuffleNode(getUNPCKLOpcode(VT) dl, VT, V1, V2, DAG); >> >> why would this not be: >> >> if (X86::isUNPCKLMask(SVOp)) >> return SVOp; > > Ok, I discovered that Bruno did this in revisions 112934, 112942 and > 113020 but the logs don't really make clear why. I did figure out that > I needed new SDNode defs for VUNPCKLPSY and VUNPCKLPDY and corresponding > patterns. Once I added them everything started working. > > I found this all very confusing because it appears there are now two > ways...