Description of problem: Somehow lremovexattr() seems to fail when running rsync Version-Release number of selected component (if applicable): rsync-3.1.3-8.fc30.x86_64 How reproducible: always Steps to Reproduce: 1. rsync -aAXHS --del --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found","/srv/backup/*"} /* $RSYNCDIR/$date Actual results: rsync: rsync_xal_set: lremovexattr("/srv/backup/rsync/2019-10-23T09-55-09/srv/backup","security.selinux") failed: Permission denied (13) Expected results: No error message Additional info: fixed in RHEL? See https://access.redhat.com/errata/RHBA-2014:1642 See also https://www.reddit.com/r/linuxquestions/comments/8lairz/rsync_tar_selinux_permissions_backups_permission/
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This was 'fixed' in RHEL5 by suppressing the error message so that it does not disrupt running systems. This is the explanation from the former maintainer of rsync: "rsync-2.6 does not remove extended attribute of target file in the case that this attribute has been erased in the source file. Lets call it bug. rsync-3.0 correctly tries to remove erased extended attributes. If the selinux is present on the target system, rsync can't erase security context of file and it outputs mentioned error. The behaviour of 2.6 and 3.0 is therefore identical except the informational error message." To me this message is correct and there is not much I can do about this. AFAICT the message is informational and does not interrupt the transfer as an error would. I am changing the resolution to NOTABUG in this case. If you feel that this is still a bug, feel free to reopen and we can discuss this a little bit more.