Cheers for that. Our repository is now in working order again. Will I
have lost any data or should this be fine? svnadmin dump reported a key
couldn't be found at about rev 3.
I would also like to take this oppurtunity to thank and congratulate the
SubVersion devlopers on the 1.0 release. We migrated from SourceSafe in
November 2002 and it's worked brilliantly ever since (especially
compared to SourceSafe).
Cheers.
Dave.
C. Michael Pilato wrote:
>Dave Oxley <dave@daveoxley.co.uk> writes:
>
>
>
>>It sounds like hot-copy is only an apr problem. We are using
>>db-4.2.52. Any idea about the other problems?
>>
>>
>
>Our repository on svn.collab.net just suffered a similar fate.
>'svnadmin recover' began its work and then returned DB_RUNRECOVERY.
>Running db_recover gave more detailed (albeit useless to me) info:
>"fatal region error detected". So, I still have no idea what caused
>this.
>
>I did a Berkeley dump/load cycle to fix the problem -- quickest thing
>I could think of. This little script should do a db_dump and db_load
>inline for you (making backups of the old database tables).
>
>--------------------------
>
>#!/bin/sh
>
>DB_BINDIR=/usr/local/BerkeleyDB.4.2/bin
>REPOS=/path/to/repos
>
>echo "### Dumping and loading tables"
>for i in changes \
> copies \
> nodes \
> representations\
> revisions \
> strings \
> transactions \
> uuids; do
> echo -n "### [${i}] dumping..."
> ${DB_BINDIR}/db_dump -kp ${REPOS}/db/${i} > ${i}.dump
> echo -n "moving..."
> mv ${REPOS}/db/${i} ${REPOS}/db/${i}-backup
> echo -n "loading..."
> ${DB_BINDIR}/db_load ${REPOS}/db/${i} < ${i}.dump
> echo "done."
>done
>echo "### Recovering repository"
>svnadmin recover ${REPOS}
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 25 11:58:32 2004