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.
DescriptionWelterlen Benoit
2021-02-19 11:29:04 UTC
Description of problem:
The root issue was discovered in the rear recover process when backup uses rsync with user different than root. Thus it adds the option --fake-user.
Version-Release number of selected component (if applicable):
rsync-3.1.3-9
How reproducible:
always
Steps to Reproduce:
1. $ ll
total 4
-rw-rw-r--. 1 user1 user1 5 Feb 19 06:23 file
lrwxrwxrwx. 1 user1 user1 4 Feb 19 06:23 link -> file
2.
rsync -v --fake-super -az -H --numeric-ids --delete --rsync-path=rsync user1.122.8:/home/user1/test_link /home/user1/res
The authenticity of host '192.168.122.8 (192.168.122.8)' can't be established.
ECDSA key fingerprint is SHA256:vOvan0gNmerHvowb17NjnPKS9Y4Zx7ehVkekm4m886U.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.122.8' (ECDSA) to the list of known hosts.
user1.122.8's password:
receiving incremental file list
test_link/
test_link/file
test_link/link -> file
sent 50 bytes received 167 bytes 48.22 bytes/sec
total size is 9 speedup is 0.04
[user1@localhost res]$ ll
total 0
drwxrwxr-x. 2 user1 user1 30 Feb 19 06:23 test_link
[user1@localhost res]$ ll test_link/
total 8
-rw-rw-r--. 1 user1 user1 5 Feb 19 06:23 file
-rwxrwxrwx. 1 user1 user1 4 Feb 19 06:23 link
3.
Actual results:
Links are not recreated
Expected results:
Links with correct permissions and owner are recreated
Additional info:
I understand that a file with xattr is created to store the permissions details, but how to use them to restore the links ?
Hello,
In fact, I was disturbed by the use of rsync in rear.
The arg must be:
---
--rsync-path="rsync --fake-super" or -M--fake-super to use the option fake-user on remote server ...
---
Thanks !