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:
man lvmvdo states:
Disable or enable compression and deduplication for VDO pool LV (the volume that maintains all VDO LV(s) associated with it).
lvchange --compression [y|n] --deduplication [y|n] VG/VDOPoolLV
However, you can do the lvchange by specifying the vdo pool lv or the
vdo lv created from the vdo pool lv.
Version-Release number of selected component (if applicable):
NA
How reproducible:
100 %
Steps to Reproduce:
[root@localhost ~]# lvchange --compression y VG_NAME/vdo_pool ; echo $?
Logical volume VG_NAME/vdo_pool changed.
0
[root@localhost ~]# lvchange --compression n VG_NAME/vdo_lv ; echo $?
Logical volume VG_NAME/vdo_lv changed.
0
[root@localhost ~]# lvchange --compression n VG_NAME/vdo_pool ; echo $?
Logical volume VG_NAME/vdo_pool already uses --compression n.
5
Expected results:
Either an error that this is not supported on the vdo lv or that we
update the man page to stipulate that it's OK to do the lvchange on either.
Additional info:
Comment 1Jonathan Earl Brassow
2020-09-17 14:50:35 UTC
For this moment - the behavior is lvchange --compression & --deduplication follows i.e. setting of --permission rw|r.
If there is wanted some other logic - we need to open new bug about making options consistent in some way.
The original logic was to return error when setting already has the value set.
Over the time many setting slipped in with returning 0 when the option already had the value set and introduced large level
of inconsistency.
Basic inspiration I think come from aligning it with i.e.:
'lvremove vg/lv' - if such LV is already gone - user gets error.
'lvcreate --name some_existing_name' - LV with existing name returns errors since already exists.
For current release of 8.4 - the feature is considered finished.