Created attachment 746964 [details] GDB backtrace Description of problem: gvfsd-metadata loops and constantly creates and deletes log files in ~/.local/share/gvfs-metadata/ Version-Release number of selected component (if applicable): gvfs-1.14.2-3.fc18.x86_64 How reproducible: randomly Actual results: gvfsd-metadata eats 40 % of CPU and constantly writes around 16 MB/s on my SSD! Additional info: [martix@martix ~]$ ls /home/martix/.local/share/gvfs-metadata/ home home-e90557d9.log home.RYLZZW root root-a7da8133.log uuid-2a6fc695-4bfe-4709-9c1a-be662a0ff8c5 uuid-2a6fc695-4bfe-4709-9c1a-be662a0ff8c5-ce546afc.log [martix@martix ~]$ ls /home/martix/.local/share/gvfs-metadata/ home home-d4aef8e8.log home.XJE1ZW root root-a7da8133.log uuid-2a6fc695-4bfe-4709-9c1a-be662a0ff8c5 uuid-2a6fc695-4bfe-4709-9c1a-be662a0ff8c5-ce546afc.log
Created attachment 746965 [details] strace
(In reply to comment #0) > gvfsd-metadata eats 40 % of CPU and constantly writes around 16 MB/s on my > SSD! Cool, at least the SSD manufacturers realize that lowering durability every new manufacturing process is the wrong way. *** This bug has been marked as a duplicate of bug 561904 ***
> Cool, at least the SSD manufacturers realize that lowering > durability every new manufacturing process is the wrong way. Doesn't seem appropriate to me to slam SSD manufacturers when it is gvfsd that is broken. They design for the typical use-cause, not for software that gets caught in a loop writing to disk. If you want an ultra durable disk, buy an expensive SAS drive.
(In reply to comment #3) > > Cool, at least the SSD manufacturers realize that lowering > > durability every new manufacturing process is the wrong way. > > Doesn't seem appropriate to me to slam SSD manufacturers when it is gvfsd > that is broken. They design for the typical use-cause, not for software > that gets caught in a loop writing to disk. If you want an ultra durable > disk, buy an expensive SAS drive. Indeed, my comment was sarcasm. Such bugs happen from time to time.