Re: rsync

[Panayiotis Karabassis <panayk@gmail.com>]

On 03/03/2012 06:24 πμ, lina wrote:
> On Sat, Mar 3, 2012 at 1:54 AM, Bob Proulx <bob@proulx.com> wrote:
>> lina wrote:
>>> Is it wrong when use
>>>
>>> rsync -azvu source destination
>>>
>>> sent 16 bytes  received 43 bytes  5.13 bytes/sec
>>> total size is 1507939808  speedup is 25558301.83
>>>
>>> Destination $ du -sh md_0.xtc
>>> 342M  md_0.xtc
>>>
>>> Source $ du -sh md_0.xtc
>>> 1.5G  md_0.xtc
>>>
>>> my confusion is that
>>> why it stopped copy the rest.
>> Is the time correct between your client and file system server?
>>
>>  $ touch foo ; ls -ldog --full-time foo ; date "+%F %T"
>>  -rw-rw-r-- 1 0 2012-02-28 10:42:29.000000000 -0700 foo
>>  2012-02-28 10:42:29
> source $ $ ls -ldog --full-time md_0.xtc ; date "+%F %T"
> -rw-r--r--  1 1507939808 2012-03-02 20:00:00.456168000 +0800 md_0.xtc
>
> destination $ ls -ldog --full-time md_0.xtc
> -rw-r--r-- 1 1507939808 2012-03-02 20:00:00.000000000 +0800 md_0.xtc
>
>> If the times are different by more than a second then you have clock
> Seems less than 1 second.
>
>> problems to fix.  The time is critical so that file timestamps are
>> correct so that rsync can file compare times.
>>
>> If you want to ignore time and force a bit comparison then use the
> here you mean "byte", not "bit"

If the bytes are different, so are the bits. If the bits are different,
so are the bytes. ;-)

>> rsync -c option.
>>
>>  $ rsync -aczv source destination
>>
>> Bob
>