Hide Forgot
This bug was initially created as a copy of Bug #1925530 I am copying this bug because: Also applies. Description of problem: See Upstream PR https://github.com/rear/rear/pull/2564 When having a LV in Raid, and 2 PVs making the VG, an error occurs when re-creating the VG in case Migration mode is used, which usually is the default since having multiple disks with same size make ReaR do a mapping and enter Migration mode. -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Start system layout restoration. Disk '/dev/vda': creating 'msdos' partition table Disk '/dev/vda': creating partition number 1 with name 'primary' Disk '/dev/vda': creating partition number 2 with name 'primary' Creating LVM PV /dev/vdb Creating LVM PV /dev/vdc Creating LVM PV /dev/vda2 Creating LVM VG 'data'; Warning: some properties may not be preserved... The disk layout recreation script failed -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Internally the failure happens because a "vgcreate" is used on the existing VG, no "vgremove" is ever performed. Version-Release number of selected component (if applicable): All versions, including Upstream How reproducible: Always Steps to Reproduce: 1. Install a system 2. Add 2 additional disks that will be used to host a LVM VG with *same* size /dev/vdb /dev/vdc 3. Create a Raid volume # pvcreate /dev/vdb # pvcreate /dev/vdc # vgcreate data /dev/vdb /dev/vdc # lvcreate -n vol1 -L 1G -m 1 data # mkfs.xfs /dev/data/vol1 # mount /dev/data/vol1 /mnt 4. Build a rescue image and perform a recovery Actual results: Failure Expected results: No failure Additional info: There is no easy workaround, the admin needs to edit the diskrestore.sh file.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.