The Samba-Bugzilla – Bug 2158
Rsync discontinues when large files are vanished or updated
Last modified: 2005-04-01 11:22:45 UTC
Currently i`ve been running rsync as backup util for quit some time.
It seemed the ideal solution at that time to do a incremental backup and then
tar it further on the server side.
Rsync gave me the abillity to do all my backups from client side over ssh
instead of running daemons on server and client side to get a backup done.
Currently i am stuck at a problem that keeps occuring randomly.
This due to activity on client side when doing a rsync
wrote 430305235 bytes read 3972109 bytes 117451.61 bytes/sec
total size is 28659100436 speedup is 65.99
rsync warning: some files vanished before they could be transfered (code 24) at
Couldn't complete backup at /home/bcktmp/backup.pl line 33.
I`ve read a earlier bug about this due to 2.5.7.
I`ve upgraded my rsync on both sides to 2.6.3 though problem hasn`t gone away.
I know this is normal way of rsync to act and give out an error because some
files are vanished or updated during the listing of the rsync.
But what i can`t understand is why it will not continue on with the files it
still has in its list to complete and complete the sync.
Ok it will not be 100 % completely but it will insure further processes to be
run if this option would be available ( to ignore vanished/updated files during
sync process ).
I`ve taken a real close look at all the flags that can be given but none of the
available flags point me out to the right action.
So here by i want to do a feature request for this option ( if it should be
possible to do so )..
Feature request: Tag for ignoring vanishes/updated files.
With kind regards
Rsync does not abort when it notices a vanished file -- it just reports it at
the end of the run. Your perl script (backup.pl) is aborting, however. You'll
need to have it check the error code, and ignore code 24 instead of aborting.