Hi Josh, > Quite possibly a good idea, but note that the my original report > occurred with a local filesystem, not a remote filesystem.
Are you absolutely sure that it happened on a local filesystem in your case and not on a home directory mounted over NFS?
I'm having a hard time to believe that you observed the behavior on a local filesystem since it is triggered by concurrent access problems of two instances of gvfsd-metadata running on two individual machines having access to the same filesystem over NFS.
The problem will not occur with two instances of the daemon running on the same machine, i.e. when accessing a local filesystem, since the kernel will perform concurrent accesses to the database with memory mapping.
Please see the detailed analysis by Michael Karcher on this issue where he explains why the bug only occurs when accessing the database over remote filesystems [1].
If you are really seeing this issue with local filesystems, you are really encouraged to file a new bug report.
On a sidenote, Red Hat has acknowledged this bug now in an internal bug report and is working on a proper fix now after an important customer complained seeing this issue on their machines.
Cheers, Adrian > [1] https://bugzilla.redhat.com/show_bug.cgi?id=561904#c30 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
