Re: [Burp-users] problem after upgrade 2.0.44 to 2.1.4

[Graham K. <gr...@gr...>]

On Mon, March 27, 2017 6:08 pm, Graham Keeling wrote:
> On Mon, March 27, 2017 7:11 am, Graham Keeling wrote:
>> On Sat, March 25, 2017 1:55 pm, Power Duka wrote:
>>> Hello,
>>>
>>> I have 10k+ files to backup.
>>> When i install the version 2.0.48, the first sync take 20 hous and send
>>> 10k
>>> files to  server.
>>>
>>> In the next few days, he only uploaded the modified files (~500 files)
>>> and
>>> the backup took about 30 minutes.
>>>
>>> When i update server and client to version 2.1.4, the client send 10k
>>> files
>>> again and take 20 hours to sync, but i abort the process and deleted
>>> the
>>> working (directory and link) and lockfile, downgraded to version stable
>>> and
>>> had them synchronized again, and took 30 minutes to sync (with only
>>> modified files).
>>>
>>> Now is running in stable version..
>>>
>>> Em sábado, 25 de março de 2017, Graham Keeling <gr...@gr...>
>>> escreveu:
>>>
>>>> On Fri, March 24, 2017 7:30 am, Graham Keeling wrote:
>>>> > On Fri, March 24, 2017 12:05 am, Power Duka wrote:
>>>> >> Hi,
>>>> >>
>>>> >> I'm using burp 2.0.44 on my centos7 with Windows Server client
>>>> 2.0.48,
>>>> >> and
>>>> >> works very well.
>>>> >>
>>>> >> Yesterday I updated the server and the client to version 2.1.4,
>>>> however
>>>> >> it
>>>> >> is redoing all the sync again.
>>>> >> The problem is that the client data is approximately 1.2TB and I
>>>> have
>>>> >> 400GB
>>>> >> free on the server.
>>>> >>
>>>> >> Why is it syncing all over again?
>>>> >>
>>>> >> Thanks!
>>>> >>
>>>> >> Duka
>>>> >
>>>> > Hello,
>>>> >
>>>> > I had somebody else report something similar on the github issues
>>>> list.
>>>> > I suspect that I broke something in 2.1.2 when I refactored some
>>>> code.
>>>> >
>>>> > This is why I have a 'stable' version, which is currently 2.0.54.
>>>>
>>>>
>>>> Hello,
>>>>
>>>> I have not yet been able to reproduce what I thought the problem is.
>>>> It probably isn't due to my refactoring.
>>>>
>>>> Can you explain in more detail what you mean by 'redoing all the sync
>>>> again'?
>>
>>
>> Hello,
>>
>> I still haven't been able to reproduce the problem.
>>
>> If you are able to reproduce it reliably, are you able to figure out in
>> exactly which version the problem appeared?
>> 2.1.0, 2.1.2, or 2.1.4?
>>
>> Is it only happening for Windows clients?
>
> I am now able to see the problem on my Debian machine.
> It is definitely a problem introduced in 2.1.2.
> I will try to fix this for the next release.

It is now fixed in master.