On 2015-07-04 16:10, Paul Slootman wrote: > Then you should exclude such mounts from the backup, e.g. by adding > xdev: 1 > to the dirvish.conf for that tree.
Actually I do have "xdev: 1" for /home. Rsync still tries to access the moint point, but fails, and the whole backup is considered failed. I wonder if Dirvish could see that it was just a mounted filesystem that failed, and ignore the issue, especially when "xdev: 1" has been specified. I now checked my failed backup and the only problem in practice seems to be that there's no access for users to the backup directory. All the files, except the mount point, still seem to be there, which is most important. With sshfs mounts the root problem is with FUSE: https://www.agwa.name/blog/post/how_fuse_can_break_rsync_backups http://fuse.996288.n3.nabble.com/force-allow-root-td11417.html My solution now is to a system-wide alias for Bash: alias sshfs='sshfs -o allow_root' So at least sshfs mounts made via command promt don't cause this problem. - Harri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
