Stefan Sperling <stsp <at> elego.de> writes:
> Using a binary file that had been committed to a revision that was > corrupt, we could construct a test case with simply committing this > file in a loop and running 'svnadmin verify' on the HEAD revision > right after. The corruption occurred in about 1 in 100 revisions. > Symptoms were like in http://subversion.tigris.org/issues/show_bug.cgi? id=3705 > The commit itself succeeded so Subversion believed the data had been > committed fine. Only a subsequent 'svnadmin verify' found the problem. This seems such an edge case, are there any normal or regular conditions in which this corruption can occur? Will it *only* happen if the revision you are commiting to is corrupt? could it happen for regular source (text files) Reason I ask is that a quick trawl shows that subversion possibly defends against these earlier version of APR http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664451 Do you understand why the corruption is occurring ?
