Matt McCutchen (m...@mattmccutchen.net) wrote on 13 September 2009 16:53:
>On Sat, 2009-09-12 at 18:22 -0300, Carlos Carvalho wrote:
>> Sanjay Acharya (svachary...@gmail.com) wrote on 11 September 2009 11:02:
>> >How is rsync supposed to behave when I give the --delete-excluded?
>>
>> >From the manual for the --delete option:
>>
>> If the sending side detects any I/O errors, then the deletion of
>> any files at the destination will be automatically disabled.
>> This is to prevent temporary filesystem failures (such as NFS
>> errors) on the sending side causing a massive deletion of files
>> on the destination.
>
>Unfortunately, this safety feature is partially disabled when rsync uses
>protocol 30 (default for rsync 3.0.*) with incremental recursion and
>--delete-during, because it caused a deadlock that could not be fixed
>without breaking protocol compatibility; see commit
>deea1f70bd67c6cc9249def9164f5e61e786e845 .
Searching in the gitweb I didn't find this commit. How can I discover
it? Also, I see no mention of this in the changelog.
What's the exit status in this case? From what Sanjay says:
Sanjay Acharya (svachary...@gmail.com) wrote on 11 September 2009 11:02:
>rsync: readlink_stat("/mnt/raid-backup/Documents/Finance") failed:
>Input/output error (5)
it appears to be 5. Could it be 23 as well? 23 is very frequent and
usually not a problem.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
