search for: posix

...-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-59cff93fe622....

Hi, I want to use the SMB3 POSIX extensions in the latest Samba (with SMB3.1.1, vers=3.1.1). By following the user manual, I have added the "posix" mount option when mounting, but it shows the following error messages. Error messages: [xxxxx] CIFS VFS: Server does not support mounting with posix SMB3.11 extensions. [xxx...

...): > > [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-473...

...sp. 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.so(trash_t...

...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/6...

The manual entry for as.POSIX says this about time zone codes... Usage as.POSIXct(x, tz = "") tz A timezone specification to be used for the conversion... but it fails to mention what these "specifications" are. So far, I have tried... as.POSIX(x, tz="UTC") ... works, gives UTC times as.PO...

...e 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-...

...;> [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...

...is not a recognized processor for this target (ignoring processor) 'arm1026ej-s' is not a recognized processor for this target (ignoring processor) In file included from ./gthr-default.h:1, from ../../llvm-gcc/gcc/gthr.h:114, from ../../llvm-gcc/gcc/unwind-dw2.c:42: ../../llvm-gcc/gcc/gthr-posix.h:43:21: error: pthread.h: No such file or directo ry ../../llvm-gcc/gcc/gthr-posix.h:44:20: error: unistd.h: No such file or director y In file included from ./gthr-default.h:1, from ../../llvm-gcc/gcc/gthr.h:114, from ../../llvm-gcc/gcc/unwind-dw2.c:42: ../../llvm-gcc/gcc/gthr-posix.h:46: error:...

...t; >> [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/gv2a2/....

...tions 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...

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

..._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_h...

...gt; >> 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/gluste...

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...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-hand...

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

Hey everyone, after we finished the introduction of the new posix acl api last cycle we still left the generic POSIX ACL xattr handler around for two reasons. First, because a few filesystems relied on the ->list() method of the generic POSIX ACL xattr handlers in their ->listxattr() inode operation. Second, during inode initalization in inode_init_always()...

...>>> 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] >>>>>>...

On Jan 1, 2011, at 8:29 PM, akramul azim wrote: > Hi, > I am planning to follow the steps to install LLVM for the ARM-target (Processor: Xscale, Architecture: armv5te): > > 1. Install binutils-2.21 (downloaded from gnu.org) > > Steps: > > $ ./configure --target=arm-unknown-linux-gnueabi --program-prefix=arm- --prefix > =/llvm/arm