On 8/30/2017 11:04 AM, Grant Drake wrote:
> Stefan wrote:
>> Just quickly skimming through this mail, this sounds like the problem
>> described and investigated in late July:
>> Note that the issue reported in that mail was not fixed in 1.8.19 (it's
>> currently expected to get into 1.8.20).
>> If you are in fact running into that described problem, try svnadmin
>> load -M 0 as a workaround. If that won't work, you are likely running
>> into a different issue here. As danielsh already suggested, try to
>> verify that indeed you don't have two different files with the same
>> sha-1 hash (I doubt that atm, though).
> I I had indeed read that thread before I posted here, however the last message on that thread said the fix would be in 1.8.19. Which is why I posted - that the fix is still pending is news to me :-)
> I have tried the svnadmin load -M 0 trick, and that does seem to work to allow the dump to be loaded. Exactly why I have no clue though of course, but thanks! Is there any downside to this?
The only downside I'm aware of is that svnadmin load performs a bit less
performant (most notably with large repositories on slower storage
systems (i.e. HDD or NAS)). This however only applies to the performance
of running the load command. The repository's performance is not
impacted to my knowledge.
P.S. your mail signature is not quite suitable for posting on mailing
Received on 2017-08-30 11:42:17 CEST