Bug 615279
| Summary: | directory size check should use st_blocks, not st_size | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Kratochvil <jan.kratochvil> |
| Component: | abrt | Assignee: | Denys Vlasenko <dvlasenk> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 15 | CC: | anton, dvlasenk, iprikryl, jmoskovc, kklic, mtoman, npajkovs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-07 13:59:09 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
Jan Kratochvil
2010-07-16 10:50:55 UTC
ping, still cannot use ABRT. I got an advice about blacklists but it does not work, it gets applied too late: BlackListedPaths = ..., */gdb/testsuite* abrt[21705]: saved core dump of pid 21702 (/home/.../gdb/testsuite/gdb.base/bigcore) to /var/spool/abrt/ccpp-1298389302-21702.new/coredump (1019277312 bytes) abrtd: Directory 'ccpp-1298389302-21702' creation detected abrtd: Size of '/var/spool/abrt' >= 1000 MB, deleting 'ccpp-1298389278-21604' abrtd: Blacklisted executable '/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/bigcore' abrtd: Corrupted or bad crash /var/spool/abrt/ccpp-1298389302-21702 (res:2), deleting Verified on: abrt-1.1.17-1.fc14.x86_64 Actually the workaround is to increase the max report size in /etc/abrt/abrt.conf: MaxCrashReportsSize = <YOUR NEW MAXIMUM> the default is 1000 MB and with the wrong size check in abrt it will decide to delete your core. (In reply to comment #2) > MaxCrashReportsSize = <YOUR NEW MAXIMUM> This workaround works, thanks. BTW it is still just a workaround. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This bug still exists, bumping to F15. *** This bug has been marked as a duplicate of bug 679720 *** |