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.
Bug 1947064 - The use of rsync with a user different than root will not restore links during the recovery
Summary: The use of rsync with a user different than root will not restore links durin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.9
Hardware: All
OS: All
urgent
high
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On: 1930662
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-07 15:16 UTC by Welterlen Benoit
Modified: 2024-06-14 01:09 UTC (History)
5 users (show)

Fixed In Version: rear-2.4-14.el7_9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-11 17:36:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear/rear/commit/d90c4904c62844b4813fd6ce240a904fdfb65286 0 None None None 2021-06-28 15:23:09 UTC
Github rear rear pull 2577 0 None open Fix rsync --fake-super option on remote server 2021-04-07 15:18:18 UTC
Github rear rear pull 2632 0 None closed Cleanup rsync and fix error reporting 2021-06-28 15:18:07 UTC
Red Hat Knowledge Base (Solution) 5894681 0 None None None 2021-04-07 15:18:30 UTC
Red Hat Product Errata RHBA-2022:0069 0 None None None 2022-01-11 17:36:13 UTC

Description Welterlen Benoit 2021-04-07 15:16:06 UTC 
This bug was initially created as a copy of Bug #1930662

I am copying this bug because: 
The issue is sneaky, we can backup and restore without error, but the system will not be usable.


Description of problem:
With a the use of rsync + user, the restore will not recreate links, because of --fake-root option of rsync:

BACKUP_URL=rsync://user1.122.220:/home/user1/rear/

Version-Release number of selected component (if applicable):
rear-2.4-17.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. rear mkbackup with BACKUP_URL=rsync://user1.122.220:/home/user1/rear/
2. rear recover
3.

Actual results:
All links are replaced by files: (/bin /lib)
---
drwxr-xr-x 18 root root  4096 Feb 15 07:19 .
drwxr-xr-x  4 root root    80 Jan 29 13:16 ..
-rw-------  1 root root     0 Feb 15 07:48 .autorelabel
-rwxrwxrwx  1 root root     7 Apr 23  2020 bin
drwxr-xr-x  6 root root  1024 Jan 29 13:54 boot
drwxr-xr-x 16 root root  4096 Feb 15 07:46 dev
drwxr-xr-x 88 root root  4096 Feb 15 07:48 etc
drwxr-xr-x  3 root root  4096 Apr 23  2020 home
-rwxrwxrwx  1 root root     7 Apr 23  2020 lib
-rwxrwxrwx  1 root root     9 Apr 23  2020 lib64
drwx------  2 root root 16384 Jan 15 10:40 lost+found
drwxr-xr-x  2 root root  4096 Apr 23  2020 media
drwxr-xr-x  3 root root  4096 Feb  9 20:35 mnt
drwxr-xr-x  2 root root  4096 Apr 23  2020 opt
drwxr-xr-x  2 root root  4096 Feb  9 15:59 proc
drwxr-x---  5 root root  4096 Feb 15 07:48 root
drwxr-xr-x  2 root root  4096 Feb  9 16:05 run
-rwxrwxrwx  1 root root     8 Apr 23  2020 sbin
drwxr-xr-x  2 root root  4096 Apr 23  2020 srv
drwxr-xr-x  2 root root  4096 Feb  9 15:59 sys
drwxrwxrwx  2 root root  4096 Feb 15 07:19 tmp
drwxr-xr-x 12 root root  4096 Jan 15 10:46 usr
drwxr-xr-x 21 root root  4096 Jan 15 10:55 var
---

Files are used to store permissions details in xattr but are not restored in recover phase.

Expected results:
We should see links:
---
lrwxrwxrwx.   1 root root    7 Apr 23  2020 bin -> usr/bin
lrwxrwxrwx.   1 root root    7 Apr 23  2020 lib -> usr/lib
lrwxrwxrwx.   1 root root    9 Apr 23  2020 lib64 -> usr/lib64
lrwxrwxrwx.   1 root root    8 Apr 23  2020 sbin -> usr/sbin
---

Additional info:
if we don't use -fake-root, the links are recreated, but the owner is wrong.
Comment 12 errata-xmlrpc 2022-01-11 17:36:05 UTC 
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 (rear bug fix and enhancement update), 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/RHBA-2022:0069
Note You need to log in before you can comment on or make changes to this bug.