On Fri, 2 Oct 2020 19:42:03 +0200, Daniel Sahlberg
wrote:
>Den fre 2 okt. 2020 kl 18:24 skrev Bo Berglund :
>
>> We are using this setup:
>> - Main server is running on Windows Server 16 Standard using VisualSVN
>> version 3.7.0, which apparently uses svn 1.9.7
>>
>> - The server is using svnsync
Den fre 2 okt. 2020 kl 18:24 skrev Bo Berglund :
> We are using this setup:
> - Main server is running on Windows Server 16 Standard using VisualSVN
> version 3.7.0, which apparently uses svn 1.9.7
>
> - The server is using svnsync nightly to synchronize over the Internet
> to a mirror SVN server
We are using this setup:
- Main server is running on Windows Server 16 Standard using VisualSVN
version 3.7.0, which apparently uses svn 1.9.7
- The server is using svnsync nightly to synchronize over the Internet
to a mirror SVN server version 1.9.7 running on Ubuntu 18.04 Server on
a different
It's definitely not a unique occurrence. Colleague of mine encountered this
too recently. Our repository's working copy size is ~1TB populated with
files around 5MB. This exception pops up during cleanup operation (probably
after an interrupted update), preventing it from finishing. As the working