#1295 PR closed: Multipathing when BOOT_OVER_SAN=y

Labels: enhancement, won't fix / can't fix / obsolete

schabrolles opened issue at 2017-04-14 12:04:

Force Loading multipath modules when BOOT_OVER_SAN is True.
Before this changes, multipath module was loaded only if multipath devices were present in LAYOUT_FILE.
So, if you migrate from virtual machine (non-multipath) to BOOT_OVER_SAN system (usually multipathed), multipath is not loaded during recover/migration.

I propose to automatically the load of multipath modules during recovery when BOOT_OVER_SAN is True.

I also add /lib*/multipath which where missing when creating rescue image with BOOT_OVER_SAN=y

schabrolles commented at 2017-04-17 12:01:

@gdha @jsmeix I'm going to close this Pull request and re-open it. (new pull request is #1309)
I've added some other commit not related to this particular issue, sorry for that.
So I prefer to separate them in separated issue in order to discuss with you about them.

I worked a lot this weekend on solving some multipathing issue (especially during migration on different system). I'm gonna push those pull request after finishing my migration testing.

  • sles11 (non-multipath) on System A <=> sles11 multipathed on System B
  • sles12 (non-multipath) on System A <=> sles12 multipathed on System B
  • rhel7 (non-multipath) on System A <=> rhel7 multipathed on System B
  • rhel6 (non-multipath) on System A <=> rhel6 multipathed on System B
  • ubuntu16.04 (non-multipath) on System A <=> ubuntu16.04 multipathed on System B

[Export of Github issue for rear/rear.]