possible / likely explanation is that there is no guarantee that blockdev will exit after kernel has put events into the udev queue. so udevadm could have run and found an empty queue.
possible / likely explanation is that there is no guarantee that blockdev will exit after kernel has put events into the udev queue.
so udevadm could have run and found an empty queue.