Description of problem: A sequence of steps can wipe out the permissions set on a directory. Version-Release number of selected component (if applicable): RHGS 3.5.0 How reproducible: Consistently Steps to Reproduce: [root@rhgs313-6 ~]# gluster volume create vol1 192.168.122.6:/bricks/brick1/vol1-1 volume create: vol1: success: please start the volume to access data [root@rhgs313-6 ~]# gluster v start vol1 volume start: vol1: success [root@rhgs313-6 ~]# mount -t glusterfs -s 192.168.122.6:/vol1 /mnt/fuse1 [root@rhgs313-6 fuse]# cd /mnt/fuse1 [root@rhgs313-6 fuse1]# mkdir dir1 [root@rhgs313-6 fuse1]# cd dir1/ [root@rhgs313-6 dir1]# getx /bricks/brick1/vol1-*/dir1 getfattr: Removing leading '/' from absolute path names # file: bricks/brick1/vol1-1/dir1 security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0xbf9444c0f8614d81a5758ed801e9f7e0 trusted.glusterfs.dht=0x000000000000000000000000ffffffff trusted.glusterfs.mdata=0x010000000000000000000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6 [root@rhgs313-6 dir1]# gluster v add-brick vol1 192.168.122.6:/bricks/brick1/vol1-2 force volume add-brick: success [root@rhgs313-6 dir1]# ll total 0 Check the directory permissions and xattrs on the bricks [root@rhgs313-6 dir1]# ll /bricks/brick1/vol1-* /bricks/brick1/vol1-1: total 0 drwxr-xr-x. 2 root root 6 Jun 4 13:50 dir1 /bricks/brick1/vol1-2: total 0 drwxr-xr-x. 2 root root 6 Jun 4 13:50 dir1 [root@rhgs313-6 dir1]# getx /bricks/brick1/vol1-*/dir1 getfattr: Removing leading '/' from absolute path names # file: bricks/brick1/vol1-1/dir1 security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0xbf9444c0f8614d81a5758ed801e9f7e0 trusted.glusterfs.dht=0x000000000000000000000000ffffffff trusted.glusterfs.mdata=0x010000000000000000000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6 # file: bricks/brick1/vol1-2/dir1 security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0xbf9444c0f8614d81a5758ed801e9f7e0 trusted.glusterfs.dht=0x00000000000000000000000000000000 trusted.glusterfs.mdata=0x010000000000000000000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6000000005cf629cf00000000302dadf6 From the mount point, cd one level up and then back again into dir1. [root@rhgs313-6 dir1]# cd .. [root@rhgs313-6 fuse1]# cd dir1 [root@rhgs313-6 dir1]# ll /bricks/brick1/vol1-* Actual results: [root@rhgs313-6 dir1]# ll /bricks/brick1/vol1-* /bricks/brick1/vol1-1: total 0 d---------. 2 root root 6 Jun 4 13:50 dir1 /bricks/brick1/vol1-2: total 0 d---------. 2 root root 6 Jun 4 13:50 dir1 Expected results: total 0 drwxr-xr-x. 2 root root 6 Jun 4 13:50 dir1 /bricks/brick1/vol1-2: total 0 drwxr-xr-x. 2 root root 6 Jun 4 13:50 dir1 Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:3249