Bug 1211575
| Summary: | Hanging FDs left over by dmeventd | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Nenad Peric <nperic> |
| Component: | lvm2 | Assignee: | Marian Csontos <mcsontos> |
| lvm2 sub component: | dmeventd (RHEL6) | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | agk, cmarthal, heinzm, jbrassow, msnitzer, prajnoha, prockai, thornber, zkabelac |
| Version: | 6.7 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.140-1.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-11 01:16:30 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: | |||
|
Description
Nenad Peric
2015-04-14 11:03:25 UTC
Narrowed down to one test which generates these hanging FDs: ./revolution_9 -i 2 -j 1 -w EXT -F -o tardis-02 -e kill_random_legs So creating raid devices, having some I/O and killing off legs causes this issue. (In reply to Nenad Peric from comment #2) > Narrowed down to one test which generates these hanging FDs: > > ./revolution_9 -i 2 -j 1 -w EXT -F -o tardis-02 -e kill_random_legs > > So creating raid devices, having some I/O and killing off legs causes this > issue. Can you paste exact commands that were run? that may be difficult, as the test is a looping test designed to stress LVM RAID by doing I/O, killing legs, checking for survival, reviving the devices, and repeating - all while doing 'lvs', 'pvs', and other operations. It would be nice to know which commands are the ones resulting in the stray FDs. Zdenek has made a lot of changes recently. This may well be fixed. I will retest with upstream and either close it or get it fixed. New dmevent in lvm2 2.02.133 handles resources in a better way. Previously there used to be a race on access & close of control fd which may have lead to desctriptor leakage. Marking verified in the latest rpms. I ran many iterations of this test case and never saw more than two or three open FDs during or after the test completed. 2.6.32-615.el6.x86_64 lvm2-2.02.141-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 lvm2-libs-2.02.141-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 lvm2-cluster-2.02.141-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 udev-147-2.71.el6 BUILT: Wed Feb 10 07:07:17 CST 2016 device-mapper-1.02.115-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 device-mapper-libs-1.02.115-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 device-mapper-event-1.02.115-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 device-mapper-event-libs-1.02.115-2.el6 BUILT: Wed Feb 10 07:49:03 CST 2016 device-mapper-persistent-data-0.6.2-0.1.rc1.el6 BUILT: Wed Feb 10 09:52:15 CST 2016 cmirror-2.02.141-2.el6 BUILT: Wed Feb 10 07:49:03 CST 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-0964.html |