Marking this bug verified in the latest rpms.
kernel-4.18.0-141.el8 BUILT: Fri Aug 30 10:51:22 CDT 2019
lvm2-2.03.05-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
lvm2-libs-2.03.05-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
lvm2-dbusd-2.03.05-4.el8 BUILT: Sun Aug 18 11:46:32 CDT 2019
lvm2-lockd-2.03.05-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
device-mapper-1.02.163-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
device-mapper-libs-1.02.163-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
device-mapper-event-1.02.163-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
device-mapper-event-libs-1.02.163-4.el8 BUILT: Sun Aug 18 11:44:11 CDT 2019
device-mapper-persistent-data-0.8.5-2.el8 BUILT: Wed Jun 5 10:28:04 CDT 2019
We updated our scenarios that do thousands of lv/pv creates to also add in unique lv tags to each, similar to comment #0, thus causing thousands of additional VG mda writes and saw no command failures. We did however see plenty of "bcache no new blocks for fd" warnings which I believe will be removed/fixed in rhel8.2
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3654