Aaah, thanks for the insight. RSYNC must transfer the file regardless of the
link count, but it also takes note of the missing link. So, it probably
considers an inode with multiple links "resolved" only after it finds a
brother/sister link and deletes the duplicate.
This would be consiste
On 26.06.2010 09:01, Rob Thompson wrote:
>
> Hello,
>
> I have a question regarding using the --recursive option when
> preserving hard link with -H. How is it, that these two options are
> compatible when used together? I would think that RSYNC would need to
> see all files/inodes before tr
On Mon, May 3, 2010 at 8:30 AM, Carlos Carvalho wrote:
> 3.1, including the latest version, produces bogus ---stats output: [...]
> Total file size: -6,417,895,484,864,819,269 bytes
>
This turned out to be an issue with with the F_LENGTH() accessor for a large
file that had a nano-second modified
Hello,
I have a question regarding using the --recursive option when preserving hard
link with -H. How is it, that these two options are compatible when used
together? I would think that RSYNC would need to see all files/inodes before
transferring, to preserve hard links. But yet it still s
