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 1791056 - "vdo stop" hangs in uds on systems with many cores
Summary: "vdo stop" hangs in uds on systems with many cores
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Matthew Sakai
QA Contact: Filip Suba
URL:
Whiteboard:
: 1791046 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-14 18:34 UTC by John Wiele
Modified: 2021-09-06 15:24 UTC (History)
3 users (show)

Fixed In Version: 6.2.3.108
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:01:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4551 0 None None None 2020-11-04 02:01:46 UTC

Description John Wiele 2020-01-14 18:34:43 UTC
Description of problem:

On PPC and AArch systems with more than 16 cores, "vdo stop" hangs.

Version-Release number of selected component (if applicable):


How reproducible:

Very

Steps to Reproduce:
1. Create and start VDO on a PPC or AArch system with >16 cores
2. Do "vdo disableDeduplication"
3. Do "vdo stop".

Actual results:

 vdo command hangs.

Expected results:

 vdo stop returns after vdo volume is stopped.

Additional info:

Comment 1 John Wiele 2020-01-14 18:37:47 UTC
*** Bug 1791046 has been marked as a duplicate of this bug. ***

Comment 2 Ken Raeburn 2020-05-27 11:05:49 UTC
It appears the core count may be a distraction. In the failures where we've got kernel logs so far, it always appears to be the case that a UDS index save is started by disabling deduplication, and then before the save finishes, the main part of the test concludes, and during cleanup, shuts down VDO, in the process triggering another save action. Various assertions fire because the first hasn't finished (though sometimes it does manage to finish just after the second save has been initiated; sometimes it doesn't ever finish, at least not before the test saves away the logs), and so the "dmsetup remove" thread never completes its action, hanging the test permanently.

Whether there's something about the core count that contributes to the time required for the save, or if it's just coincidence, is uncertain. More cores mean more UDS zones in the default configuration (default zone count = cores/2, up to MAX_ZONES=16), and the zones' data are saved sequentially, though with the buffering I'm not sure that makes much difference.

Comment 7 Filip Suba 2020-09-04 14:06:32 UTC
Verified with kmod-kvdo-6.2.3.114-74.el8.

Comment 10 errata-xmlrpc 2020-11-04 02:01:16 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 (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


Note You need to log in before you can comment on or make changes to this bug.