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.
Description of problem:
The current name of the device-mapper target for VDO is "dedupe". In order to bring the target name consistent with the "dm-vdo" project direction, the target name should change to "vdo".
Version-Release number of selected component (if applicable):
kmod-kvdo-6.1.0.98-11.el7.x86_64
(This is also present in kmod-kvdo-6.1.0.114-11.el7)
How reproducible:
100%
Steps to Reproduce:
1. Type "dmsetup targets".
Actual results:
The output contains the line "dedupe v6.1.0".
Expected results:
The output contains the line "vdo v6.1.0"
Additional info:
This would affect, among other things, the "dmsetup create" command, which would change the following "dmsetup create" command:
dmsetup create vdo1 --uuid VDO-4e4a5056-68a3-4491-971d-9e995b36beaa --table '0 929357480 dedupe /dev/nvme0n1 4096 disabled 0 32768 16380 on sync vdo1 ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
...to:
dmsetup create vdo1 --uuid VDO-4e4a5056-68a3-4491-971d-9e995b36beaa --table '0 929357480 vdo /dev/nvme0n1 4096 disabled 0 32768 16380 on sync vdo1 ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
Creating VDO with new version of vdo rpm but old (pre-change) of kmod-kvdo leads to ioctl error unknown dmsetup target. I expect very similar behaviour the other way around. This is acceptable as we are not yet past GA.
# dmsetup targets
vdo v6.1.0
dmsetup create vdo_test --uuid VDO-205cfa88-79c5-4e03-b206-4e1e8a019ae5 --table '0 12556528 vdo /dev/sdb 4096 disabled 0 32768 16380 on auto vdo_test ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
The dm target name is changed, setting to verified.
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/RHEA-2018:0900