Guten Tag Paul E, am Donnerstag, 10. Januar 2013 um 21:11 schrieben Sie: > This is a major issue for us as we're actively developing against > these projects and having to recommit over and over again. Currently > resolving the issue by creating a dump to the revision prior to the > truncation and then loading into a new repository, but this is costing > development time.
Something is corrupting your repository, but your on your own to find the problem. From what I've read it's most likely a hardware or OS problem, for example your filesystem may be corrupted. I had similar issues some years ago with a virtualized Windows where for some reason the filesystem broke two times in one weak and the only solution was to create a new file system and restore into this from backup. Have a look at your event viewer, do checkdisk, maybe even memory tests, you can even try to monitor disk access with Process Monitor form Sysinternals to see if something occurs. But first of all I would implement a good backup process, e.g. using svnsync and hooks or something similar, as it doesn't sound you are prepared for loss of revision files. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
