Bug 847291
Summary: | abrt gets stuck if the "worst dir" is not a "problem directory" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Göran Uddeborg <goeran> |
Component: | libreport | Assignee: | abrt <abrt-devel-list> |
Status: | CLOSED ERRATA | QA Contact: | Miroslav Hradílek <mhradile> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | dkutalek, dvlasenk, jmoskovc, jraising, mhradile, nobody+abrt-devel-list, tlavigne |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libreport-2.0.9-12.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 07:54:12 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
Göran Uddeborg
2012-08-10 13:08:26 UTC
Fixed in git: commit 3f74a39f2bee037ee81ac2937b85f2141b3a83e5 Author: Denys Vlasenko <vda.linux> Date: Mon Aug 13 14:50:29 2012 +0200 abrtd: make it ignore non-problem dirs when looking for a dir to delete A related upstream commit: commit 4d7cf343acae679cb849007150428f7becce2210 Author: Denys Vlasenko <vda.linux> Date: Thu Dec 20 10:34:29 2012 +0100 Make get_dirsize_find_largest_dir less talkative Correction (different git commit ID): commit 8391c228db600525d515e94f66d7c73d47c663a6 Author: Denys Vlasenko <vda.linux> Date: Thu Dec 20 15:03:29 2012 +0100 Make get_dirsize_find_largest_dir less talkative Cause Directory not created by ABRT was in /var/spool/abrt Consequence ABRT got stuck in infinite loop when reaching it's hard disk space quota. Fix Ignore unknown directories when counting freespace in /var/spool/abrt Result abrtd not caught in the infinite loop 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. http://rhn.redhat.com/errata/RHBA-2013-0290.html |