gvfsd-metadata on nfs homes produces large number of nfs requests
Bug #720927 reported by
Gökdeniz Karadağ
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:/
Summary: gvfsd-metadata enters a loop where it continually creates and renames files under $HOME/.
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.
Changed in gvfs (Ubuntu): | |
status: | New → Confirmed |
Changed in gvfs (Debian): | |
status: | Unknown → New |
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.
We are also seeing this issue. I think our interim strategy will be to make gvfsd-metadata not executable. Gnome seems okay without it.