Für andere (mir ist bewusst, dass das Thema alt ist):
/home/xxx/.gvfs in der /etc/rsnapshot.conf auszunehmen hilft bei mir.
Das Verzeichnis ist soweit ich recherchiert habe, dazu da Serverfreigaben und so zu mounten, für das Backup also irrelevant (man könnte sie direkt abgreifen).
Deshalb hat darauf erst einmal auch root keinen Zugriff.
Das wiederum sorgt dafür, dass rsnapshot nicht reinkommt und dann das hier greift:
That is a safety mechanism. If there was an error, the lists may be in
error, and a deletion may take out a whole lot more than you want. Picture
getting permissions on a large section of the source directory messed up
so the rsync process can't see into them. The send list now does not
include everything down there, but it can be seen, and deleted, on the
destination. Generally, users would prefer to rectify the problems on the
source end and re-run the sync, rather than losing large quantities on the
destination end.
This safety mechanism can be overridden, by the "--ignore-errors" flag. If
you're taking the default --delete behaviour, wherein it deletes before
the transfer (can be overridden by "--delete-after"), these errors are in
the filelist generation stage, not problems of insufficient space, or
dropped connection. If you do, in fact, have a place you can't read on
the destination or source, and it should be that way, exclude it. That
way, it won't hit it and error, so you can both run your sync with
deletes, and still have it try not to ruin your life over a little
problem.
Quelle: http://lists.samba.org/archive/rsync/2004-June/009891.html
Wenn das Verzeichnis excludet ist, dann kann rsnapshot wieder überall hin und traut sich auch wieder alte Dateien zu löschen.
giks
