I ran into an issue where multipathd wasn't tracking a multipath device that was created by the multipath command. It turns out that if multipathd fully initialized a path device, and that device later goes offline and then a multipath device that could use that path is created by multipath, multipathd will attempt to reload the device to use the offline path, which will fail. This will cause it to not track the multipath device at all.
The first patch fixes this. The second patch allows mutipathd to track these offline paths that should belong to a device, and add them to device once they come back online. The third patch is just a cleanup. Benjamin Marzinski (3): multipathd: monitor new multipath dev even if we can't update it multipathd: re-add paths skipped because they were offline multipathd: don't update paths in INIT_MISSING_UDEV libmultipath/print.c | 1 + libmultipath/structs.h | 5 ++++ libmultipath/structs_vec.c | 5 ++++ multipathd/main.c | 59 ++++++++++++++++++++++++++++++++++++-- 4 files changed, 67 insertions(+), 3 deletions(-) -- 2.48.1
