Again, the error in rsync prototocol

[Alexander Lamb]

I will file this at Apple.
Here is a more detailed log:

($:~)-> sudo rsync -Eavvb --delete --backup-dir="/Volumes/DATA 1/ 
rsync_bck" /Volumes/DATA/ "/Volumes/DATA 1"
Password:
backup_dir is /Volumes/DATA 1/rsync_bck/
building file list ...
[sender] expand file_list to 131072 bytes, did move
[sender] expand file_list to 262144 bytes, did move
[sender] expand file_list to 524288 bytes, did move
[sender] expand file_list to 1048576 bytes, did move
done
[receiver] expand file_list to 131072 bytes, did move
[receiver] expand file_list to 262144 bytes, did move
[receiver] expand file_list to 524288 bytes, did move
[receiver] expand file_list to 1048576 bytes, did move
[receiver] expand file_list to 131072 bytes, did move
[receiver] expand file_list to 262144 bytes, did move
[receiver] expand file_list to 524288 bytes, did move
[receiver] expand file_list to 1048576 bytes, did move
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at / 
SourceCache/rsync/rsync-20/rsync/io.c(359)

The receiver is the same as the sender since I am doing a local backup.
The only "bizarre" thing I might have done is the following:

On MacOSX, you can choose between UFS, HFS+, HFS+ Journaled, HFS+  
Journaled with case sensitive.

Well, for maybe some Unix nostalgia, I have my volume as HFS+  
Journaled WITH case sensitiveness and my destination drive is only HFS 
+ Journaled :-)

I will try to change this because even FileVault on MacOSX doesn't  
like this!

Alex

On Jul 3, 2005, at 5:52 PM, Wayne Davison wrote:

> On Wed, Jun 29, 2005 at 11:43:01AM +0200, Alexander Lamb wrote:
>
>> I am doing something really simple. It worked twice and now fails for
>> an unknown reason.
>>
>
> The output you showed indicates that rsync finished building the file
> list, transferred that list from the sender to the receiver, the
> receiving side built is own delete-file-list, and then the receiving
> side died for some reason (though it didn't mention why).  You might
> try turning on core dump to see if rsync is crashing.  You might also
> try adding one extra -v (to the two already there) to see exactly what
> rsync is doing at the time it fails.  Finally, since you're using a
> modified rsync, the problem may well be in the modified code for  
> MacOS,
> so you'd need to talk to the folks you tweaked rsync about the  
> failure.
>
> ..wayne..
>

--
Alexander Lamb
Service d'Informatique Médicale
Alexander.J.Lamb at sim.hcuge.ch
+41 22 372 88 62
+41 79 420 79 73