Re: Having rsync issues when modified part of file isnt at end

[Shachar S. <sh...@sh...>]

rsyncrypto compresses as part of the encryption. You obviously did not
notice this, as you were using /dev/random as your source, and hence
producing uncompressible files. This is also the reason (at least part
of it) that the encrypted files were not the same size.

On 03/02/15 10:34, Guillaume Friloux wrote:
> The only thing i can see is that between file1.iso.enc and 
> file2.iso.enc,
> the filesize dropped a little, and between file2.iso.enc and 
> file3.iso.enc it is higher,
> but i have no idea if this can be related...
You are using rsync with --inplace. In that mode, rsync cannot reuse
blocks that were already overwritten by the destination file. When the
new file is bigger than the old one, you are overwriting the data you
would reuse while transferring, severely limiting rsync's ability to
optimize your transfer. If you remove --inplace, you will see that rsync
has no problem optimizing your encrypted files, no matter the size changes.

You have not asked your gzip question, but I am guessing it is either
the same issue there, or you forgot to pass it the --rsyncable flag.

Shachar