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 1025456 - mirror device failure scenarios lead to deadlocks (part 2)
Summary: mirror device failure scenarios lead to deadlocks (part 2)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jonathan Earl Brassow
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1009700
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 18:24 UTC by Corey Marthaler
Modified: 2016-04-08 21:19 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1009700
Environment:
Last Closed: 2015-03-26 16:14:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Jonathan Earl Brassow 2014-07-26 02:54:43 UTC 
The test listed in the last comment seems to fail one device first and then a second.  The second failure happens while the mirror is being up-converted due to the first repair.

I need to know a couple things to determine whether to fix this issue:
1) is it reproducible (It'd be useful to see those results and compare)
2) what is the result of the failure?  Is the mirror usable at that point or not?  Failure at an intermediate stage would be the same as bug 1016296, and I would likely close WONTFIX if there is no solution.  (RAID does not suffer from these issues.)

It is possible that we just need to cope with the fact that the final repair is called on the up-converting tmp image.  This could be a simple fix but depends on the answer to #2.
Comment 2 Jonathan Earl Brassow 2014-08-26 15:48:12 UTC 
Moving to rhel6.7 for further consideration.  Whether to close or not will depend on the answers to the questions in comment 1.
Comment 4 Jonathan Earl Brassow 2015-03-26 16:14:12 UTC 
(In reply to Jonathan Earl Brassow from comment #2)
> Moving to rhel6.7 for further consideration.  Whether to close or not will
> depend on the answers to the questions in comment 1.

Closing WONTFIX.

You are welcome to reopen this bug to be reconsidered if answers are provided to comment 1.
Comment 6 Corey Marthaler 2016-04-08 21:19:50 UTC 
Filed bug 1325457 for the specific multiple asynchronous mirror device failures mentioned in that last few comments of this bug.
Note You need to log in before you can comment on or make changes to this bug.