Comment 21 for bug 517021

I've seen this behaviour even when the harddrive isn't full. It eats CPU and hits the harddrive with thousands of ioops per second (seen using iotop). I've left it running for eight hours once, hoping it would sort itself out. Deleting ~/.local/share/gvfs-metadata and restarting the daemon "solves" the problem, but destruction is a terrible way to fix a problem, and it doens't prevent the problem from happening again days or weeks later.