Bug 557104
Summary: | dmeventd crash if both snapshot and mirror monitoring DSO are used | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Milan Broz <mbroz> |
Component: | lvm2 | Assignee: | Petr Rockai <prockai> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.5 | CC: | agk, cmarthal, dwysocha, edamato, heinzm, jbrassow, mbroz, prockai, pvrabec, zkabelac |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-30 09:01:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milan Broz
2010-01-20 12:46:44 UTC
Fix in upstream cvs -> POST. Patch in lvm2-2_02_56-6_el5. Is this message still expected in the latest rpms? device-mapper: waitevent ioctl failed: Interrupted system call The segfault in this bug is verified fixed in lvm2-2.02.56-6.el5. I also verified that multiple VGs containing multiple snaps/mirrors also works. Waiting to put this into the VERIFIED state until the question in comment #6 is answered. (In reply to comment #6) > device-mapper: waitevent ioctl failed: Interrupted system call yes, it is expected. dmeventd has one thread per monitored device, every thread waits for event (in dm-ioctl syscall). If the device is removed waiting is interrupted. This warning should be probably more quite (like debug level only) but it is just cosmetic change. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0298.html |