excessive tracker disk i/o post-resume from suspend-to-*

[Markus Kienast]

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.

[Ewan Dunbar (ewan-dunbar)]

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.

[mihai.ile (mihai.ile)]

Well I killed trackerd and when I resume from suspend no longer makes intense use of hdd.
The problem is that after 2 or 3 more suspends I get hdd activity again.. Last one last for 10min until finally stopping.
I completely uninstalled tracker from my system, rebooted and made some 10-15 sleep/resume with and without compiz activated and everything works great but after that it began again to use the hdd on resume but only one time. Now I think I suspended some 20+ times and only happened one time.
For me it's completely random... have no idea why is happening, what uses the hdd on resume but only sometimes...
So in my case has nothing to do with tracker.
Using atop to track hdd activity per process it does not show which process uses the hdd but in the summary I get 100% use of hdd (see attachment), I think it has to do with the red line starting with "PAG | scan...", have no Idea what that means...

Do you still have this issue?!