Bug 451100
| Summary: | system constantly freezing due to (pointless) disk activity | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Sean Middleditch <sean> |
| Component: | firefox | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | CC: | robatino |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-13 18:15:58 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
Sean Middleditch
2008-06-12 19:24:51 UTC
Try installing iotop (yum install iotop) to see what's causing the disk activity. There's a good chance it's firefox, I see the same thing, though it's not so bad on my system. It's been reported as bug #439908. From iotop, something very close to this was always in the top three lines during the last 85 seconds that my hard disk has been constantly churning. 1432 root 0 B/s 7.60 K/s 0.00 % 99.99 % [kjournald] 3056 elanthis 212.92 K/s 91.25 K/s 0.00 % 94.53 % firefox 235 root 0 B/s 0 B/s 0.00 % 38.02 % [pdflush] Not a lot is being written if I understand that right, but I guess the journal is being flushed or something, which does sound like the Firefox fsync bug. I also looked up Pidgin and apparently it is well known that it also has excessive disk writing and fsyncing, although not nearly as bad as Firefox, which explains why it seems to contribute to this. There are already upstream bugs for that one. Since I seem to have pretty much just confirmed that it's the good ol' firefox fsync bug and that I'm just getting hit by it way harder than most, I'll close this as a duplicate. Sorry for the noise. *** This bug has been marked as a duplicate of 439908 *** |