It looks like udev is responding to legitimate received events, based on 'udevadm monitor -e'. Commenting out the add|change action in 95-multipath.rules stops the spurious events and returns CPU consumption to expected levels.
It looks like udev is responding to legitimate received events, based on 'udevadm monitor -e'. Commenting out the add|change action in 95-multipath.rules stops the spurious events and returns CPU consumption to expected levels.