gvfs-fuse causes rsync to fail

[satyriasis]

Binary package hint: gvfs

gvfs and gvfs-fuse 0.2.5-0ubuntu2
Ubuntu 8.04.1
Linux 2.6.24-19-generic
rsync 2.6.9-6ubuntu2

I maintain backups using dirvish, which writes sequential images using rsync. Dirvish is set up to back up parts of my root partition and my home partition to a third partition. The rsync command run by dirvish (to back up my home partition) is:

rsync -vrltH --delete -pgo --stats -D --numeric-ids -x \
--exclude-from=/snapshot/satyr-home/20080731-home/exclude \
--link-dest=/snapshot/satyr-home/20080730-home/tree /home/ \
/snapshot/satyr-home/20080731-home/tree

Upon normal login to a GNOME desktop, $HOME/.gvfs has the following permissions:

jorge@satyr:~$ ls -ld .gvfs
dr-x------ 2 jorge jorge 0 2008-08-01 18:37 .gvfs

When dirvish attempts to back up my home partition with ~/.gvfs in the preceding condition, it fails with the following rsync error:

rsync: readlink "/home/jorge/.gvfs" failed: Permission denied (13)
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]

A similar rsync command to back up my root partition terminates successfully.

In order to run rsync on my home partition, I source a script from ~/.profile that includes the following:

/bin/fusermount -zu $HOME/.gvfs
/usr/lib/gvfs/gvfs-fuse-daemon $HOME/.gvfs

That gives me a directory with the following permissions:

jorge@satyr:~$ ls -ld .gvfs
drwx------ 2 jorge jorge 4096 2008-07-26 22:11 .gvfs

With ~/.gvfs so constituted, rsync successfully backs up my /home partition, and dirvish terminates with 0.

I've had this problem over the last three upgrades to gvfs and its cousins. I'm not experiencing any other problems related to .gvfs, but this one seems relatively serious to me.

I apologize if this is a duplicate report.

Thanks for looking into it.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 225361, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.