On Fri, 2022-01-28 at 16:57 +0100, Martin Wilck wrote: > > It's a race condition. It probably happens while multipathd is > reloading a map (*), suspending it during the table reload. The > device > will be resumed a few fractions of a second later (so yes, it's > "quick"), but then it's too late More precisely: The suspend state itself may actually not last longer than a few ms. But once the symlink is bent to point to the wrong device, it will remain so, until the CHANGE event following the device resume is successfully processed by udev, which may happen substantially later. And it's that longer time span which matters for systemd's mount attempt (or LVM device activation, for that matter). Martin -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
