Bug 1077405
| Summary: | Various dm_task_run failures cause many continuing problems in LVM | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> |
| lvm2 sub component: | Mirroring and RAID | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | high | CC: | agk, cmarthal, dwysocha, heinzm, jbrassow, msnitzer, mspqa-list, nperic, prajnoha, prockai, skito, thornber, tlavigne, zkabelac |
| Version: | 7.0 | Keywords: | Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.152-1.el7 | Doc Type: | Bug Fix |
| Doc Text: |
dmeventd code has been updated to recent version which includes numerous fixes, including fixes for various possible errors issued about dm_task_run calls.
|
Story Points: | --- |
| Clone Of: | 813954 | Environment: | |
| Last Closed: | 2016-11-04 04:07:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 813954 | ||
| Bug Blocks: | 445253, 644071, 654116, 1049888, 1113520, 1203710, 1205796, 1295577, 1313485 | ||
|
Comment 2
RHEL Program Management
2014-03-25 05:47:20 UTC
I'm convinced it could be matched with Bug #1108540 since dmeventd is directly involved. It's fixed with release of 2.02.112 We need to inspect more here - I don't think this is exactly the same as bug #1108540 - the errors differ. While in bug #1108540 we always had "dm_task_run failed, errno = 6, No such device or address", here we have "dm_task_run failed, errno = 22, Invalid argument" which seems to be a different issue (wrong table supplied while dmeventd is trying to fixup LVs). New dmeventd code in version 2.02.133 should resolve most of spurious dm_task_run errors flowing out of dmeventd process. My view here is - once we release this version - and we get another fail case with dm_task_run - take it as a new bug. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions I have not seen any of these messages in quite some time on any of the nodes doing raid regression testing. Marking verified. 3.10.0-480.el7.x86_64 lvm2-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 lvm2-libs-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 lvm2-cluster-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 device-mapper-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 device-mapper-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 device-mapper-event-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 device-mapper-event-libs-1.02.131-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 device-mapper-persistent-data-0.6.3-1.el7 BUILT: Fri Jul 22 05:29:13 CDT 2016 cmirror-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 sanlock-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016 sanlock-lib-3.4.0-1.el7 BUILT: Fri Jun 10 11:41:03 CDT 2016 lvm2-lockd-2.02.161-3.el7 BUILT: Thu Jul 28 09:31:24 CDT 2016 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://rhn.redhat.com/errata/RHBA-2016-1445.html |