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 (kmod-kvdo bug fix and enhancement update), 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:7778
Description of problem: [sweettea@localhost ~]$ sudo vdo create --name vdo0 --device /dev/fedora_localhost-live/vms Creating VDO vdo0 Logical blocks defaulted to 6802574 blocks. The VDO volume can address 26 GB in 13 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. Starting VDO vdo0 Starting compression on VDO vdo0 VDO instance 0 volume is ready at /dev/mapper/vdo0 [sweettea@localhost ~]$ sudo lvcreate --size 2G --snapshot --name vms_snap /dev/fedora_localhost-live/vms Logical volume "vms_snap" created. [sweettea@localhost ~]$ sudo vdo import --name vdo0-snap --device /dev/fedora_localhost-live/vms_snap Importing VDO vdo0-snap vdo: ERROR - UUID df61bc46-13dc-4091-bdec-4896c744888c already exists in VDO volume(s) stored on /dev/disk/by-id/dm-uuid-LVM-Gexh1cit2vwmcvIf2AAvullg3mWvrnql0SluovtpLXaYGoyPw84zRD4NPmGO3Nu4 [sweettea@localhost ~]$ sudo vdo import --name vdo0-snap --device /dev/fedora_localhost-live/vms_snap --uuid usage: vdo import [-h] -n <volume> --device <devicepath> [--activate {disabled,enabled}] [--blockMapCacheSize <megabytes>] [--blockMapPeriod <period>] [--compression {disabled,enabled}] [--deduplication {disabled,enabled}] [--emulate512 {disabled,enabled}] [--maxDiscardSize <megabytes>] [--uuid <uuid>] [--vdoAckThreads <threadCount>] [--vdoBioRotationInterval <ioCount>] [--vdoBioThreads <threadCount>] [--vdoCpuThreads <threadCount>] [--vdoHashZoneThreads <threadCount>] [--vdoLogicalThreads <threadCount>] [--vdoLogLevel {critical,error,warning,notice,info,debug}] [--vdoPhysicalThreads <threadCount>] [--writePolicy {async,async-unsafe,sync,auto}] [-f <file>] [--logfile <pathname>] [--verbose] vdo import: error: argument --uuid: expected one argument [sweettea@localhost ~]$ sudo vdo import --name vdo0-snap --device /dev/fedora_localhost-live/vms_snap --uuid '' Importing VDO vdo0-snap Starting VDO vdo0-snap Starting compression on VDO vdo0-snap VDO instance 1 volume is ready at /dev/mapper/vdo0-snap Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: