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.
Bug 1505961 - KVDO - DedupeQ thread starts with capital letter
Summary: KVDO - DedupeQ thread starts with capital letter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kmod-kvdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: corwin
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-24 16:36 UTC by Dennis Keefe
Modified: 2021-09-03 12:03 UTC (History)
4 users (show)

Fixed In Version: 6.1.0.34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 16:25:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0900 0 None None None 2018-04-10 16:26:06 UTC

Description Dennis Keefe 2017-10-24 16:36:52 UTC 
Description of problem:

Deduplication thread "DedupeQ" starts with a capital D.  All other threads 
start with lowercase letters.

Version-Release number of selected component (if applicable):
vdo-6.1.0.0-6.x86_64
kmod-kvdo-6.1.0.0-4.el7.x86_64


How reproducible:

Steps to Reproduce:
1. Create VDO volume
2. ps aux|grep vdo
root     13621  0.0  0.0   6672   876 pts/4    S+   Oct19   0:00 less vdoCreate.log
root     19812  0.2  0.0      0     0 ?        S    10:41   0:18 [kvdo562:DedupeQ]
root     19813  0.2  0.0      0     0 ?        S    10:41   0:17 [kvdo562:journal]
root     19814  0.2  0.0      0     0 ?        S    10:41   0:17 [kvdo562:packerQ]
root     19815  9.1  0.0      0     0 ?        S    10:41  10:10 [kvdo562:logQ0]
root     19816  0.2  0.0      0     0 ?        S    10:41   0:17 [kvdo562:physQ0]
root     19817  0.2  0.0      0     0 ?        S    10:41   0:17 [kvdo562:hashQ0]
root     19818  1.1  0.0      0     0 ?        S    10:41   1:19 [kvdo562:bioQ0]
root     19822  3.2  0.0      0     0 ?        S    10:41   3:33 [kvdo562:ackQ]
root     19823  3.2  0.0      0     0 ?        S    10:41   3:33 [kvdo562:cpuQ0]



Actual results:
DedupeQ

Expected results:
dedupeQ

Additional info:
Comment 6 Jakub Krysl 2017-11-21 11:29:05 UTC 
kmod-kvdo 6.1.0.55-9.el7

# ps aux|grep vdo
root     14054  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:dedupeQ]
root     14055  0.5  0.0      0     0 ?        S    11:26   0:00 [kvdo0:journalQ]
root     14056  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:packerQ]
root     14057  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:logQ0]
root     14058  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:physQ0]
root     14059  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:hashQ0]
root     14060  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:bioQ0]
root     14061  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:bioQ1]
root     14062  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:bioQ2]
root     14063  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:bioQ3]
root     14064  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:ackQ]
root     14065  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:cpuQ0]
root     14066  0.2  0.0      0     0 ?        S    11:26   0:00 [kvdo0:cpuQ1]
root     14068  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14069  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14070  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14071  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14072  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14073  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14074  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14075  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14076  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14077  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14078  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14079  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:indexW]
root     14080  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:reader]
root     14081  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:reader]
root     14082  0.0  0.0      0     0 ?        S    11:26   0:00 [kvdo0:writer]
root     14093  0.0  0.0 112704   980 pts/0    S+   11:28   0:00 grep --color=auto vdo
Comment 9 errata-xmlrpc 2018-04-10 16:25:27 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.