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 using ReaR to backup/restore a system, it shows a successful backup. But it failed to restore
Version-Release number of selected component (if applicable):
rear-2.4-2.el7.x86_64
How reproducible:
Steps to Reproduce:
1. Run 'rear -d -v mkbackup' backup a system on the client.
2. Restore 'rear recover' the system on another testing client
Actual results:
#### The backup client disk and lvm status.#####
~~~
[root@rhel7local ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 rhel lvm2 a-- 7.31g 40.00m
/dev/sdb dockervg lvm2 a-- <10.00g 6.97g
[root@rhel7local ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
docker-pool dockervg twi-a-t--- 3.00g 17.42 11.04
root rhel -wi-ao---- 6.47g
swap rhel -wi-ao---- 820.00m
~~~
#### The restored client status
[root@rhel7local ~]# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 rhel lvm2 a-- 7.31g 40.00m
[root@rhel7local ~]# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
root rhel -wi-ao---- 6.47g
swap rhel -wi-ao---- 820.00m
[root@rhel7local ~]# ll /dev/sd*
brw-rw----. 1 root disk 8, 0 Feb 4 17:53 /dev/sda
brw-rw----. 1 root disk 8, 1 Feb 4 17:53 /dev/sda1
brw-rw----. 1 root disk 8, 2 Feb 4 17:53 /dev/sda2
brw-rw----. 1 root disk 8, 3 Feb 4 17:53 /dev/sda3
brw-rw----. 1 root disk 8, 16 Feb 4 17:53 /dev/sdb
Expected results:
The ReaR could restore the thin pool layout on the new client.
Additional info:
Renaud, this sounds like bz1450667, I remember you were working on that one, do you have any idea? Wasn't that fixed properly, or is it a different case?