Comment 3 for bug 1912031

In my experience this happens when the LVM filtering is not configured to ignore all new volumes, so it constantly scans new volumes attached to the host using os-brick.

Specifically happens when there are leftover volumes, in other words, we have a block device under /dev but the storage array is no longer exporting/mapping that volume to the host, so the device cannot read or do anything.

Removing these leftover devices fixes the blocked LVM call, though the right solution is setting the global_filter in /etc/lvm/lvm.conf