Bug 444171
| Summary: | RHEL5 cmirror tracker: potential memory leak during I/O load | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | cmirror | Assignee: | Jonathan Earl Brassow <jbrassow> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.2 | CC: | agk, ccaulfie, dwysocha, edamato, heinzm, mbroz |
| 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: | 2009-01-20 21:27:15 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
Corey Marthaler
2008-04-25 16:30:45 UTC
I was using xiogen/xdoio for the I/O load. There were no failure scenarios of any kind taking place during this. On each node in cluster: /dev/mapper/hayes-mirror1 on /mnt/mirror1 type gfs (rw,hostdata=jid=2:id=131073:first=0) /dev/mapper/hayes-mirror2 on /mnt/mirror2 type gfs (rw,hostdata=jid=2:id=262145:first=0) /dev/mapper/hayes-mirror3 on /mnt/mirror3 type gfs (rw,hostdata=jid=2:id=393217:first=0) /dev/mapper/hayes-mirror4 on /mnt/mirror4 type gfs (rw,hostdata=jid=2:id=524289:first=0) for i in 1 2 3 4; do xiogen -f buffered -m random -s read,write,readv,writev -t 100 -T 1000000 -F 1000000:/mnt/mirror$i/$(hostname) | xdoio -n 15 -kvD & done commit 4eca59fdacf347d0315eff78487b642e17be2de7
Author: Jonathan Brassow <jbrassow>
Date: Fri May 16 13:16:23 2008 -0500
clogd: Fix 444171 [memory leak]
If there was an invalid request to the cluster
log server, it would ignore it. This is fine, but it
did not free the memory structure holding the invalid
request.
I've also taken this opportunity to explicitly state
all valid requests, and let the 'default' case handle
the errors.
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/RHEA-2009-0158.html |