← Back to team overview

desktop-packages team mailing list archive

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

 

See the "remote bug watches" on the right here. It links to gnome-bugs
#637095 <https://bugzilla.gnome.org/show_bug.cgi?id=637095> , which is
FIXED.

Given that this bug can trash SSDs on hardware level, by making so many
writes that the lifespan is considerably reduced, by doing billions of
write calls in a matter of hours, I'm asking for a hotfix in Ubuntu
12.04 precise.

Given that SSDs are silent, a user wouldn't even notice this unless he
has a CPU or disk meter or similar showing. I do, but I still missed
this once and it ran for 10 hours overnight IIRC.

How can we escalate this for a hotfix in a stable distro? I don't know
launchpad well enough. Could somebody please make some noise? There's
already a straight-forward fix, and commited to the GNOME repo, it's
just a matter of shipping it for the stable Ubuntu distros.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

Status in gvfs package in Ubuntu:
  Confirmed
Status in gvfs package in Debian:
  Fix Released

Bug description:
  Binary package hint: gvfs

  My disk space was really full at one moment, no byte left free. People say, that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the gvfsd-metadata can't read it without being screwed up.
  Workaround: run "rm -rf ~/.local/share/gvfs-metadata"

  Expected results:
  gvfsd-metadata should be able to handle the no space left situation.

  
  --- Original description ---
  After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC.
  Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer).

  Please fix this because it is highly annyoing. Right now i am killing
  it every 20s with the watch command to be able to work at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions