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.
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:0989
# vdo create --name vdo --device /dev/mapper/vg-lv --verbose mkdir -p /run/lock/vdo touch /run/lock/vdo/_etc_vdoconf.yml.lock chmod 644 /run/lock/vdo/_etc_vdoconf.yml.lock touch /run/lock/vdo-config-singletons Creating VDO vdo grep MemAvailable /proc/meminfo pvcreate -qq --test /dev/mapper/vg-lv vdo: ERROR - Device /dev/mapper/vg-lv excluded by a filter. # dnf install vdo-6.2.0.298-10.el8_0.x86_64.rpm --snip-- Upgraded: vdo-6.2.0.298-10.el8_0.x86_64 Complete! # vdo create --name vdo --device /dev/mapper/vg-lv --verbose Creating VDO vdo grep MemAvailable /proc/meminfo pvcreate --config devices/scan_lvs=1 -qq --test /dev/mapper/vg-lv blkid -p --no-part-details /dev/mapper/vg-lv modprobe kvdo vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/disk/by-id/dm-uuid-LVM-fXs5kEnYX9D92qZDG1uqEXi3gSrGMvg9GVOLNDKII17Jz23afvNCpAGODdLfA6hi vdodumpconfig /dev/disk/by-id/dm-uuid-LVM-fXs5kEnYX9D92qZDG1uqEXi3gSrGMvg9GVOLNDKII17Jz23afvNCpAGODdLfA6hi Starting VDO vdo dmsetup status --target vdo vdo grep MemAvailable /proc/meminfo modprobe kvdo vdodumpconfig /dev/disk/by-id/dm-uuid-LVM-fXs5kEnYX9D92qZDG1uqEXi3gSrGMvg9GVOLNDKII17Jz23afvNCpAGODdLfA6hi vdodumpconfig /dev/disk/by-id/dm-uuid-LVM-fXs5kEnYX9D92qZDG1uqEXi3gSrGMvg9GVOLNDKII17Jz23afvNCpAGODdLfA6hi dmsetup create vdo --uuid VDO-9b323f29-0d44-4fa4-a149-4830795ebbc7 --table '0 19487242776 vdo V2 /dev/disk/by-id/dm-uuid-LVM-fXs5kEnYX9D92qZDG1uqEXi3gSrGMvg9GVOLNDKII17Jz23afvNCpAGODdLfA6hi 2441608192 4096 32768 16380 on auto vdo maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1' dmsetup status --target vdo vdo Starting compression on VDO vdo dmsetup message vdo 0 compression on vdodmeventd -r vdo dmsetup status --target vdo vdo dmsetup status --target vdo vdo VDO instance 0 volume is ready at /dev/mapper/vdo