Description of problem: If a file has setuid bit set and if it is migrated through remove-brick then setuid bit disappears after migration. Version-Release number of selected component (if applicable): 3.4.0.59rhs-1.el6_4.x86_64 How reproducible: always Steps to Reproduce: 1.creted a 6x2 distributed-replicate volume 2. added a new user test and created some files on the mount point as test user 3. set the sticky bit and setuid bit chmod +t <file> & chmod +s <file> 4. permission becomes -rwSrwSr-T 5. Now remove one of the pair using remove-brick command gluster volume remove-brick <vol> <brick> start 6. once the migration is complete commit it 7. check the permissions on the mount point Actual results: permission of the file got changed to -rw-rwSr-T. so setuid bit is missing for user Additional info: [root@rhs-client4 ~]# gluster v info Volume Name: dist-rep Type: Distributed-Replicate Volume ID: fccb1682-2a43-4925-a030-d303aaa43352 Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: rhs-client4.lab.eng.blr.redhat.com:/home/dist-rep0 Brick2: rhs-client9.lab.eng.blr.redhat.com:/home/dist-rep1 Brick3: rhs-client4.lab.eng.blr.redhat.com:/home/dist-rep4 Brick4: rhs-client9.lab.eng.blr.redhat.com:/home/dist-rep5 Decommissioned bricks ---------------------- rhs-client4.lab.eng.blr.redhat.com:/home/dist-rep6 rhs-client9.lab.eng.blr.redhat.com:/home/dist-rep7 cluster info --------------- rhs-client9.lab.eng.blr.redhat.com rhs-client40.lab.eng.blr.redhat.com rhs-client4.lab.eng.blr.redhat.com client ------ 10.70.35.26 mount type nfs mount point 10.70.35.26:/nfs attached the sosreports mount was on
Followed the repro steps and checked the permissions of the file after the migration. The permissions are intact. Closing the bug.
Please review and sign-off edited doc text.
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://rhn.redhat.com/errata/RHBA-2015-0038.html
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days