Agreed that the data in the known-good copy should replace the data in other copies
Disagreed that we should recommnd rsync'ing db/ to a portable disk over hotcopy to such a disk Philip Martin wrote on Wed, Nov 02, 2011 at 17:39:06 +0000: > Daniel Shahaf <d...@daniel.shahaf.name> writes: > > > Apache Wiki wrote on Wed, Nov 02, 2011 at 16:49:37 -0000: > >> + Copy, by any convenient method (such as rsync or by physically shipping > >> a disk), the following parts of the mirror repository into the master > >> repository: > >> + > >> + * the 'db' subdirectory > > > > It doesn't make any sense to copy the entire db/ directory. Instead of > > that the advice should be to dump or svnsync-from the known-good source. > > The slave is the best known-good source. > > This is an issue 3845 repository. We haven't identified how many rev > files are corrupt through truncation. If we do fix a corrupt rev file > with information from the slave then offsets within the rev file change > and subsequent rev files that refer to the old offsets become corrupt. > > -- > uberSVN: Apache Subversion Made Easy > http://www.uberSVN.com
