On Sat, 2022-01-29 at 21:05 +0100, Zdenek Kabelac wrote: > Dne 29. 01. 22 v 0:21 Martin Wilck napsal(a): > > > > > AFAICS my patch eliminates the window for this error entirely. > > > Ok now I see that there is already skip for DM_SUSPENDED > and you patch likely only tries to preserve some existing state of > links. > > I'll need to get in touch with Peter here. > > I guess the idea behind was to avoid read of device that will be > resumed and > will automatically get a new event - and suspened device itself > cannot change Thank you! > - but that fact it's been loosing existing state was missed - I'm > wondering > why this was not seen as problem before. One reason is that we're now starting multipathd earlier. This has a lot of advantages, but it reveals problems that were hidden behind the "After=systemd-udev-settle.service" dependency of mulltipathd before. Regards, Martin -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
