Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When sending files with the --xattrs, if a file is read-only and has new extended
attributes, a non-root receiving user can fail to set the new attributes.
Version-Release number of selected component (if applicable):
rsync-3.1.3-9.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
$ rm -rf orig a
$ touch orig a
$ setfattr -n user.attrib -v value orig
$ chmod -w orig a
$ rsync -av --xattrs orig a
Actual results:
sending incremental file list
rsync: rsync_xal_set: lsetxattr(""/home/casantos/a"","user.attrib") failed: Permission denied (13)
sent 129 bytes received 123 bytes 504.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1179) [sender=3.1.2]
Expected results:
Files should be synchronized without errors.
Additional info:
It is possible to circumvent the problem by means of the --fake-super argument
$ rsync -av --fake-super --xattrs orig a
sending incremental file list
sent 164 bytes received 21 bytes 370.00 bytes/sec
total size is 0 speedup is 0.00
The problem has been reported upstream a log time ago and is still not fixed.
Description of problem: When sending files with the --xattrs, if a file is read-only and has new extended attributes, a non-root receiving user can fail to set the new attributes. Version-Release number of selected component (if applicable): rsync-3.1.3-9.el8.x86_64 How reproducible: Always Steps to Reproduce: $ rm -rf orig a $ touch orig a $ setfattr -n user.attrib -v value orig $ chmod -w orig a $ rsync -av --xattrs orig a Actual results: sending incremental file list rsync: rsync_xal_set: lsetxattr(""/home/casantos/a"","user.attrib") failed: Permission denied (13) sent 129 bytes received 123 bytes 504.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1179) [sender=3.1.2] Expected results: Files should be synchronized without errors. Additional info: It is possible to circumvent the problem by means of the --fake-super argument $ rsync -av --fake-super --xattrs orig a sending incremental file list sent 164 bytes received 21 bytes 370.00 bytes/sec total size is 0 speedup is 0.00 The problem has been reported upstream a log time ago and is still not fixed.