excessive tracker disk i/o post-resume from suspend-to-*
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tracker (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When I resume my machine from hibernation, I get very intense HDD access. It turned out that I only have this excessive access when trackerd is running when I suspend the machine.
I have no idea what trackerd is doing there or why but it is certain that tracker is the cause, as I only get this when tracker is on.
However I tried to figure out what is going on looking at top. The last thing I saw before the excessive HDD action stopped was an ls on top of the list. Maybe tracker is performing an ls over the whole HDD? No idea. Tracker itself consumed some CPU as well. I figure that trackerd gets confused somehow when the clock suddenly leaps forward after resume.
I would like to confirm with 100% accuracy that trackerd is the cause, but I have no idea if there is something like top for HDD access or any other way to track that down.
Please advise.
Changed in tracker (Ubuntu): | |
status: | New → Confirmed |
I get the same on resume after having left the machine in S3 for a while - strangely, trackerd doesn't show up at the top of the list in top either for memory or for CPU, but it sure slows the system down until I kill it. Only since upgrading to 8.04 Beta.