Re: [dm-devel] [PATCH] multipath.rules: fix "smart" bug with failed valid path check

2023-02-09 Thread Martin Wilck
On Tue, 2023-02-07 at 18:32 -0600, Benjamin Marzinski wrote: > If "multipath -u" fails, udev doesn't import any values from the > program. This means that multipath.rules will continue to use the > values > for DM_MULTIPATH_DEVICE_PATH and FIND_MULTIPATHS_WAIT_UNTIL that it > has > already imported

Re: [dm-devel] [PATCH] multipath.rules: fix "smart" bug with failed valid path check

2023-02-08 Thread Benjamin Marzinski
On Wed, Feb 08, 2023 at 07:35:36AM +, Martin Wilck wrote: > Hello Ben, > > On Tue, 2023-02-07 at 18:32 -0600, Benjamin Marzinski wrote: > > If "multipath -u" fails, udev doesn't import any values from the > > program. This means that multipath.rules will continue to use the > > values > > for

Re: [dm-devel] [PATCH] multipath.rules: fix "smart" bug with failed valid path check

2023-02-07 Thread Martin Wilck
Hello Ben, On Tue, 2023-02-07 at 18:32 -0600, Benjamin Marzinski wrote: > If "multipath -u" fails, udev doesn't import any values from the > program. This means that multipath.rules will continue to use the > values > for DM_MULTIPATH_DEVICE_PATH and FIND_MULTIPATHS_WAIT_UNTIL that it > has > alre

[dm-devel] [PATCH] multipath.rules: fix "smart" bug with failed valid path check

2023-02-07 Thread Benjamin Marzinski
If "multipath -u" fails, udev doesn't import any values from the program. This means that multipath.rules will continue to use the values for DM_MULTIPATH_DEVICE_PATH and FIND_MULTIPATHS_WAIT_UNTIL that it has already imported from the database. This is the correct thing to do for every case except