OK - that makes sense - I'll try adding --ignore-errors. I'm not worried about risking a massive deletion since my script checks for an "unusual" change in the size of my backed up directories, so I guess I'd catch that.
I'm not sure I understand what the --backup option does or why it would solve the massive deletion problem. What does --backup do that isn't done by the params I already use (-rlvtogS)? I looked at the man page and it's not really clear on that point. On Monday, March 21, 2011, Nadav Har'El wrote: > If rsync finds a read error in the local directory, it *disables* the > --delete option, thinking that it might accidentally delete files that > weren't actually deleted - we just had files reading them. > > So my guess is that you had a read error in /home. A very common (and > very annoying) reason for such a read error is your $HOME/.gvfs, which > often causes ridiclous errors when read. > > If this is indeed your problem, you can add the "--ignore-errors" option > to rsync to ignore errors and do the --delete in spite of them. Be aware, > though, that you are risking a massive deletion of your remote system if > you have real read errors. If you also use the --backup option, this might > not be a risk - but please do the consideration yourself. -- Shlomo Solomon http://the-solomons.net Sent by KMail 1.13.3 (KDE 4.4.3) on LINUX Mandriva 2010.1 _______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
