From: Robert C. <rob...@ti...> - 2009-03-21 00:06:27
|
On Fri, 2009-03-20 at 00:35 +0000, Robert Canner wrote: > On Thu, 2009-03-19 at 10:51 +0000, Niall Brosnan wrote: > > I can confirm that I'm using a stock flexbackup 1.2.1-6 on ubuntu 8.10 > > without this issue. > > ... > > > I do get the same "find: `./.gvfs': Permission denied" entry in my > > log, > > but it is not a showstopper. What backup format and medium are you > > choosing? > > ... > > Many thanks Niall. I'm using flexbackup version 1.2.1-6, with .tar.gz > output format, writing to a 4.3GB drive in an external housing, > ... > robert@venus:~$ egrep -v -e '(^#|^$)' /etc/flexbackup.conf > $type = 'tar'; > $set{'home'} = "/home"; > ... > ... Anyway, I'm now thinking I > should try to unmount my .gvfs before allowing flexbackup to start ... Yes, that was the solution. According to 'mount', gnome-fuse-daemon was mounted on my .gvfs. I needed to unmount it before the backup. First I reverted to my original flexbackup.conf (the one without any ".gvfs" prune/exclude expressions). Then I used $ fusermount -u ~/.gvfs to unmount the daemon from .gvfs. Then $ sudo flexbackup -set home backed up /home without errors. 'find' simply treated .gvfs as an empty directory :-) Q. I didn't create .gvfs ... Where did it come from and who mounted this daemon on it? A. As far as I can tell (1) GNOME automatically creates ~/.gvfs (2) it is designed as a mount point for gnome-fuse-daemon (3) GNOME automatically mounts it. (gnome-fuse-daemon is in the gvfs-fuse package.) Q. What happens if you unmount this? Is it safe? A. It seems fairly safe. It certainly seems sensible to unmount it before root tries to back up your home directory. GNOME re-mounts it automatically next time you log in. Package versions: gvfs-fuse 0.2.3-0ubuntu4, gvfs 0.2.3-0ubuntu4, fuse-utils 2.7.2-1ubuntu2, gnome-about 1:2.22.1-0ubuntu6gnewsense1. Many thanks Niall, Robert |