|
Yeah right. I get permission denied. [geoaccount@slave ~]$ ll /bricks/brick1/brick/.glusterfs/29/d1/29d1d60d-1ad6-45fc-87e0-93d478f7331e ls: cannot access /bricks/brick1/brick/.glusterfs/29/d1/29d1d60d-1ad6-45fc-87e0-93d478f7331e: Permission denied [geoaccount@slave ~]$ ll /bricks/brick1/brick/.glusterfs/29/d1/ ls: cannot access /bricks/brick1/brick/.glusterfs/29/d1/: Permission denied [geoaccount@slave ~]$ ll /bricks/brick1/brick/.glusterfs/29/ ls: cannot access /bricks/brick1/brick/.glusterfs/29/: Permission denied [geoaccount@slave ~]$ ll /bricks/brick1/brick/.glusterfs/ ls: cannot open directory /bricks/brick1/brick/.glusterfs/: Permission denied [root@slave ~]# ll /bricks/brick1/brick/.glusterfs/29 total 0 drwx--S---+ 2 root
AD+group 50 Sep 10 07:29 16 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 33 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 5e drwx--S---+ 2 root AD+group 50 Sep 10 07:29 73 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 b2 drwx--S---+ 2 root AD+group 50 Sep 21 09:39 d1 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 d7 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 e6 drwx--S---+ 2 root AD+group 50 Sep 10 07:29 eb [root@slave ~]# However, the strange thing is that I could replicate new files and folders before. The replication is broken since the “New folder” was created. These are the permissions on a dev/test system: [root@slave-dev ~]# ll /bricks/brick1/brick/.glusterfs/ total 3136 drwx------. 44 root root 4096 Aug 22 18:19 00 drwx------. 50 root root 4096 Sep 12 13:14 01 drwx------. 54 root root 4096 Sep 13 11:33 02 drwx------. 59 root root 4096 Aug 22 18:21 03 drwx------. 60 root root 4096 Sep 12 13:14 04 drwx------. 68 root root 4096 Aug 24 12:36 05 drwx------. 56 root root 4096 Aug 22 18:21 06 drwx------. 46 root root 4096 Aug 22 18:21 07 drwx------. 51 root root 4096 Aug 22 18:21 08 drwx------. 42 root root 4096 Aug 22 18:21 09 drwx------. 44 root root 4096 Sep 13 11:16 0a I’ve configured an AD group, SGID bit, and ACLs via Ansible on the local mount point. Could this be an issue? Should I avoid configuring the permissions on .glusterfs and below? # ll /mnt/glustervol1/ total 12 drwxrwsr-x+ 4 AD+user AD+group 4096 Jul 13 07:46 Scripts drwxrwxr-x+ 10 AD+user AD+group 4096 Jun 12 12:03 Software -rw-rw-r--+ 1 root AD+group 0 Aug 8 08:44 test drwxr-xr-x+ 6 AD+user AD+group 4096 Apr 18 10:58 tftp glusterfs_volumes: […] permissions: mode: "02775" owner: root group: "AD+group" acl_permissions: rw […] # root directory is owned by root. # set permissions to 'g+s' to automatically set the group to "AD+group" # permissions of individual files will be set by Samba during creation - name: Configure volume directory permission 1/2 tags: glusterfs file: path: /mnt/{{ item.volume }} state: directory mode: "{{ item.permissions.mode }}" owner: "{{ item.permissions.owner }}" group: "{{ item.permissions.group }}" with_items: "{{ glusterfs_volumes }}" loop_control: label: "{{ item.volume }}" when: item.permissions is defined # ACL needs to be set to override default umask and grant "AD+group" write permissions - name: Configure volume directory permission 2/2 (ACL) tags: glusterfs acl: path: /mnt/{{ item.volume }} default: yes entity: "{{ item.permissions.group }}" etype: group permissions: "{{ item.permissions.acl_permissions }}" state: present with_items: "{{ glusterfs_volumes }}" loop_control: label: "{{ item.volume }}" when: item.permissions is defined Regards, Christian From: Kotresh Hiremath Ravishankar <khiremat@xxxxxxxxxx> I think I am get what's happening. The geo-rep session is non-root. Could you do readlink on brick path mentioned above
/bricks/brick1/brick/.glusterfs/29/d1/29d1d60d-1ad6-45fc-87e0-93d478f7331e from a geaccount user and see if you are getting "Permission Denied" errors? Thanks, Kotresh HR On Mon, Sep 24, 2018 at 7:35 PM Kotte, Christian (Ext) <christian.kotte@xxxxxxxxxxxx> wrote:
Thanks and Regards, Kotresh H R |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
