Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Marking Verified in the latest rpms.
kernel-5.14.0-10.el9 BUILT: Tue Oct 26 07:00:13 PM CDT 2021
lvm2-2.03.14-1.el9 BUILT: Wed Oct 20 11:22:27 AM CDT 2021
lvm2-libs-2.03.14-1.el9 BUILT: Wed Oct 20 11:22:27 AM CDT 2021
vgcreate vdo_sanity /dev/sdd1 /dev/sdc1 /dev/sde1 /dev/sdh1
WARNING: Devices have inconsistent physical block sizes (4096 and 512).
Volume group "vdo_sanity" successfully created
lvcreate --yes --type vdo -n stats_vdo -L 25G vdo_sanity -V 2T
Wiping vdo signature on /dev/vdo_sanity/vpool0.
The VDO volume can address 22 GB in 11 data slabs, each 2 GB.
It can grow to address at most 16 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Logical volume "stats_vdo" created.
stats_vdo vdo_sanity vwi-a-v--- 2.00t vpool0 0.00 vpool0(0)
attr:vwi-a-v---
pvs:['vpool0']
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 (new packages: lvm2), 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-2022:3972