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:
A new Github issue came in where a user was asking about changing the "indexSparse" setting in /etc/vdoconf.yml (which is unsupported, but not impossible) to change the size of their index. I decided to try this to see what effect this change had on the volume. I created a fresh VDO volume, wrote some data, stopped the volume, edited the config file from a 0.25/dense index to now say it is 0.25/sparse, and then started the volume. Everything came up fine, and deduplication was working. When I run `vdo status --verbose`, the output indicates that the index is Sparse, which is not the case. If I run `vdodumpconfig` against my backing device, the correct setting is displayed.
This bug is intended to adjust the behavior of VDO Manager to properly report configurations from `vdodumpconfig` when that is available, and only report the contents of /etc/vdoconf.yml when the live-data is not available. There may be other values that are also affected by this. Those should be adjusted as well if they are discovered.
Version-Release number of selected component (if applicable):
vdo-6.2.2.33-12.el8
How reproducible:
100%
Steps to Reproduce:
1. Create a VDO volume with default index settings (0.25/dense) `vdo create --name vdo0 --device /dev/loop0 --indexMem 0.25 --sparseIndex disabled`
2. Observe index setting `vdo status --verbose | grep 'Index sparse'`
3. Stop VDO volume `vdo stop --name vdo0`
4. Edit /etc/vdoconf.yml, changing "indexSparse: disabled" to "indexSparse: enabled"
5. Start VDO volume `vdo start --name vdo0`
6. Observe incorrect index setting `vdo status --verbose | grep 'Index sparse'`
7. Observe correct index setting `vdodumpconfig /dev/loop0 | grep sparse:`
Actual results:
[root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse'
Index sparse: enabled
Expected results:
[root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse'
Index sparse: disabled
Additional info:
This has no effect on the operation of the VDO volume, but should someone go in and modify this file, it can lead to confusion about its configuration.
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-2020:4551
Description of problem: A new Github issue came in where a user was asking about changing the "indexSparse" setting in /etc/vdoconf.yml (which is unsupported, but not impossible) to change the size of their index. I decided to try this to see what effect this change had on the volume. I created a fresh VDO volume, wrote some data, stopped the volume, edited the config file from a 0.25/dense index to now say it is 0.25/sparse, and then started the volume. Everything came up fine, and deduplication was working. When I run `vdo status --verbose`, the output indicates that the index is Sparse, which is not the case. If I run `vdodumpconfig` against my backing device, the correct setting is displayed. This bug is intended to adjust the behavior of VDO Manager to properly report configurations from `vdodumpconfig` when that is available, and only report the contents of /etc/vdoconf.yml when the live-data is not available. There may be other values that are also affected by this. Those should be adjusted as well if they are discovered. Version-Release number of selected component (if applicable): vdo-6.2.2.33-12.el8 How reproducible: 100% Steps to Reproduce: 1. Create a VDO volume with default index settings (0.25/dense) `vdo create --name vdo0 --device /dev/loop0 --indexMem 0.25 --sparseIndex disabled` 2. Observe index setting `vdo status --verbose | grep 'Index sparse'` 3. Stop VDO volume `vdo stop --name vdo0` 4. Edit /etc/vdoconf.yml, changing "indexSparse: disabled" to "indexSparse: enabled" 5. Start VDO volume `vdo start --name vdo0` 6. Observe incorrect index setting `vdo status --verbose | grep 'Index sparse'` 7. Observe correct index setting `vdodumpconfig /dev/loop0 | grep sparse:` Actual results: [root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse' Index sparse: enabled Expected results: [root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse' Index sparse: disabled Additional info: This has no effect on the operation of the VDO volume, but should someone go in and modify this file, it can lead to confusion about its configuration.