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:
When VDO's log level is in debug this verifyDuplicationWork can be displayed often in certain configurations. The meaning of the message is not informative.
Log message:
kernel: kvdo8:cpuQ1: verifyDuplicationWork: match - we win!
How reproducible:
100%
Steps to Reproduce:
1. create vdo volume - vdo create --name=vdo1 --/dev/sdb
2. create vdo volume - vdo create --name=vdo2 --/dev/mapper/vdo2
3. echo debug > /sys/kvdo/log_level
4. write data to vdo2
5. monitor logs
Actual results:
Log message:
kernel: kvdo8:cpuQ1: verifyDuplicationWork: match - we win!
Expected results:
Log message:
kernel: kvdo8:cpuQ1: verifyDuplicationWork: match
or
a message that is more descriptive
Additional info:
I was able to reproduce it easily with kmod-kvdo-6.1.0.72-10 on kernel 3.10.0-799. So I updated kernel to 3.10.0-820 and updated kmod-kvdo to 6.1.0.98-11. I repeated the same steps but was not able to get a single message in logs on debug log level.
Ken, is this fixed by removing the log entry altogether? And if it is the case, how to verify deduplication of certain data now?
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