Philippe Bruhat (BooK) wrote:
> On Wed, Apr 21, 2010 at 08:45:29AM +0200, Philippe Bruhat (BooK) wrote:
>> On Wed, Apr 21, 2010 at 08:35:03AM +0200, Philippe Bruhat (BooK) wrote:
>>> I understand this as rsync currently restoring the file above. Using ls -l
>>> to see the progress of the restore, I get this:
>>>
>>> -rw-r--r-- 1 esouche esouche 107368448 2010-04-05 22:47 places.sqlite
>>> -rw------- 1 root root 107216896 2010-04-21 00:00
>>> .places.sqlite.UL48SN
>> I tried restoring only this file, and watched the progress.
>> The restore got stuck at the same point:
>> -rw-r--r-- 1 esouche esouche 107368448 2010-04-05 22:47 places.sqlite
>> -rw------- 1 root root 107216896 2010-04-21 08:43 .places.sqlite.uVfJCE
>>
>
> So I tried to restore that specific file using a zip archive, only to
> discover that the old file on the target and the file being restored
> by backuppc had the same md5 and sha1 sums.
>
> Is that a known bug in rsync?
No - or at least I haven't heard of it. Could you have filesystem corruption on
either side?
--
Les Mikesell
[email protected]
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
