Hide Forgot
Description of problem: Process tracker-miner-fs eat all available CPU resources very long time. I not turned off the computer at night, the process of tracker-miner-fs worked all night and now continues to work.
I'm seeing this too. I noticed that the machine was getting way into its swapspace, which it didn't used to do, and the usage was increasing at a pretty rapid rate. Running top showed tracker-miner-fs as eating nearly 20G of VM space after just 5 days of uptime: 7394 dhowells 39 19 19.8g 11g 2344 S 0.0 72.3 6:02.08 tracker-miner-f Killing that made the system much happier and more responsive to things requiring a lot of buffer cache (GIT and compilations for example).
This happens to me too on Fedora 16. The problem is intermittent but once tracker-miner is hung it never stops. Only solution is to kill it.
Created attachment 587527 [details] System call trace for tracker-miner-fs in hung state
Created attachment 587528 [details] System call trace for tracker-miner-store in hung state
We had another one hang today and I attached system call traces before killing it. Looks like tracker-miner-fs and tracker-miner-store seem to both hang at the same time. We have NFS home directories, not sure if that could trigger it. Looks like both processes are in a loop trying to perform the same I/O sequence over and over. Possibly some kind of deadlock?
"me too" Have seen this crop up now and again under F16. Just had it happen again, which led to google and this bug report. All I had to type was "tracker-miner-fs" and google auto-suggested the rest, so it must be a common problem.
Here is a relevant bug report: https://bugzilla.redhat.com/show_bug.cgi?id=747689 Looks like tracker is an indexing tool... maybe it just takes forever to run sometimes? For now, I simply uninstalled it along with everything that depends on it.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.