Bug 1539063 - Cannot restore backup of system disk when using multipath+software raid
Summary: Cannot restore backup of system disk when using multipath+software raid
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.4
Hardware: Unspecified
OS: Linux
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: David Jež
Depends On:
TreeView+ depends on / blocked
Reported: 2018-01-26 14:51 UTC by Renaud Métrich
Modified: 2021-03-11 17:01 UTC (History)
3 users (show)

Fixed In Version: rear-2.4-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-10-30 11:43:19 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github rear rear issues 1722 0 'None' closed Cannot restore disk built on multipath + md 2020-09-08 07:25:28 UTC
Github rear rear pull 1819 0 'None' closed Issue #1722 - Cannot restore disk built on multipath + md 2020-09-08 07:25:30 UTC
Red Hat Knowledge Base (Solution) 3341091 0 None None None 2018-02-01 12:46:54 UTC
Red Hat Product Errata RHBA-2018:3293 0 None None None 2018-10-30 11:44:02 UTC

Description Renaud Métrich 2018-01-26 14:51:13 UTC
Description of problem:

Trying to restore a backup of a system booting with multipath + software raid, at the rescue prompt, after starting multipathd or executing "rear recover", the multipath devices are not found.
This is due to mdadm building the array at boot, preventing multipath from grabbing the disks later.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Setup a VM with 4 SCSI disks (2 images only to have multipath)

2. Install the system with rootvg on RAID1 on the 2 multipath disks

3. Create a rescue image ("rear mkrescue")

4. Boot the rescue image

5. Run "multipathd" and "multipath -l"

Actual results:

No multipath device listed

Additional info:

The workaround is to delete the md device:

mdadm --stop /dev/mdX

Comment 2 Renaud Métrich 2018-02-01 12:46:32 UTC
The proposed workaround is not sufficient, because as soon as the disk is touched (e.g. via parted), the MD array will be rebuilt.

The fix (on RHEL at least) is to disable the automatic array creationg udev rule /lib/udev/rules.d/65-md-incremental.rules by creating an empty file /etc/udev/rules.d/65-md-incremental.rules

This can be done by appending "touch etc/udev/rules.d/65-md-incremental.rules" to /usr/share/rear/build/GNU/Linux/110_touch_empty_files.sh:

# cat /usr/share/rear/build/GNU/Linux/110_touch_empty_files.sh
	touch etc/udev/rules.d/65-md-incremental.rules
popd >&8

Comment 3 Renaud Métrich 2018-05-28 09:36:47 UTC
Pull Request: https://github.com/rear/rear/pull/1819

Comment 4 Pavel Cahyna 2018-06-27 16:24:22 UTC
1539063 merged upstream in 2.4/89dbd45e1ad37f49421c7154813f972cb2b63a0e

Comment 9 errata-xmlrpc 2018-10-30 11:43:19 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.