gvfsd-metadata on nfs homes produces large number of nfs requests

Bug #720927 reported by Gökdeniz Karadağ
This bug report is a duplicate of:  Bug #517021: gvfsd-metadata causes 100% CPU usage. Edit Remove
86
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Medium
gvfs (Debian)
Fix Released
Unknown
gvfs (Fedora)
Unknown
Unknown
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

On our Maverick machines, we are seeing the issue described at
https://bugzilla.redhat.com/show_bug.cgi?id=561904

Summary: gvfsd-metadata enters a loop where it continually creates and renames files under $HOME/.local/share/gvfs-metadata
When home directory is on NFS, this puts excessive load on NFS server (our CPU load was 10+ before killing stray gvfs-metadata processes, afterwards it became ~0.40)

The redhat/fedora bug does not state a solution currently.

Revision history for this message
Jeff Strunk (jstrunk-math) wrote :

We are also seeing this issue. I think our interim strategy will be to make gvfsd-metadata not executable. Gnome seems okay without it.

Revision history for this message
João Neves (jneves) wrote :

Followed the information on this thread: http://ubuntuforums.org/showthread.php?t=1421580

 Will now wait to see if the problem repeats itself. It has been happening about once a day in the last week.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
John Paul Adrian Glaubitz (glaubitz) wrote :

I have added the respective bug reports in Debian and Fedora/RHEL.

Also, there is an upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=637095

FYI:

The linked Fedora/RHEL bug report contains in-depth analysis by Michael Karcher why this issue arises. He came to the conclusion that the bug cannot be easily fixed as this is a fundamental design issue.

Cheers,

Adrian

Changed in gvfs (Debian):
status: Unknown → New
Revision history for this message
John Paul Adrian Glaubitz (glaubitz) wrote :

As a subscriber of the RedHat bug report (https://bugzilla.redhat.com/show_bug.cgi?id=561904) I received a message from a non-public duplicate of this bug report in the RedHat bug tracker which has been filed by a "strategic customer". The duplicate non-public bug report has therefore increased severity and will hopefully be fixed in the future with a new upsteam/patch release.

Adrian

Changed in gvfs:
importance: Unknown → Medium
status: Unknown → New
Changed in gvfs (Debian):
status: New → Confirmed
Changed in gvfs (Debian):
status: Confirmed → Fix Released
Changed in gvfs:
status: New → In Progress
Changed in gvfs:
status: In Progress → Fix Released
Changed in gvfs:
status: Fix Released → Confirmed
Changed in gvfs:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.