Re: [PATCH 1/3] multipathd: monitor new multipath dev even if we can't update it

2025-03-27 Thread Benjamin Marzinski
On Tue, Mar 25, 2025 at 11:33:12PM +0100, Martin Wilck wrote: > On Mon, 2025-03-24 at 16:55 -0400, Benjamin Marzinski wrote: > > If a multipath device was created by the multipath command, > > multipathd > > might not agree with how the device was created. ev_add_map() can > > reload > > the device

Re: [PATCH 1/3] multipathd: monitor new multipath dev even if we can't update it

2025-03-25 Thread Martin Wilck
On Mon, 2025-03-24 at 16:55 -0400, Benjamin Marzinski wrote: > If a multipath device was created by the multipath command, > multipathd > might not agree with how the device was created. ev_add_map() can > reload > the device with a different table by calling add_map_without_path() - > > > update_m

[PATCH 1/3] multipathd: monitor new multipath dev even if we can't update it

2025-03-24 Thread Benjamin Marzinski
If a multipath device was created by the multipath command, multipathd might not agree with how the device was created. ev_add_map() can reload the device with a different table by calling add_map_without_path() -> update_map(). If this reloading of the map failed, multipathd was simply ignoring th