In FCOS, we currently disable multipath with https://github.com/coreos/fedora-coreos-config/blob/cac303b548e196ddb0f33fb9e9656ce52fea9993/manifests/fedora-coreos-base.yaml#L19.
cc @lucab @ajeddeloh @bgilbert for experiences.
cc @jlebon @cgwalters @dustymabe for opinions on x86_64.
Also a side node, with https://github.com/coreos/coreos-installer/pull/105 coming in, we should have s390x's zFCP SCSI code path to be the same as normal code path so things would be more aligned and less troubles for multipathing on s390x. Multipathing on ECKD DASD on s390x is built-in in the hardware if I understand correctly.
In FCOS, we currently disable multipath with
https://github.com/coreos/fedora-coreos-config/blob/cac303b548e196ddb0f33fb9e9656ce52fea9993/manifests/fedora-coreos-base.yaml#L19
.On RHCOS 4.2 on s390x, @steffen-maier and I can bring up multipath devices as
/sysroot
(bind mounted to/
) butgrowpart
does not work by default. Steffen came up with a patch forcoreos-growpart
. (notgrowpart
itself, which does not support multipath afaiu https://bugs.launchpad.net/nova-dpm/+bug/1750400 https://bugs.launchpad.net/cloud-init/+bug/1556260).I have not tested on FCOS but should work as the logics in
coreos-growpart
don't differ much in 2 branches. Testing on FCOS this week...Searching around I found those for CL: https://github.com/coreos/bugs/issues/2254 https://github.com/coreos/bugs/issues/2556
cc @lucab @ajeddeloh @bgilbert for experiences. cc @jlebon @cgwalters @dustymabe for opinions on x86_64.
Also a side node, with https://github.com/coreos/coreos-installer/pull/105 coming in, we should have s390x's zFCP SCSI code path to be the same as normal code path so things would be more aligned and less troubles for multipathing on s390x. Multipathing on ECKD DASD on s390x is built-in in the hardware if I understand correctly.