On 8/25/06, Dan Mercer <dmercer@8kb.net> wrote:
> Howdy Subversives,
>
> I have recently encountered what appears to be repository corruption
> resulting from a dump and load of my subversion repository.
>
> Here are the particulars:
>
> * Subversion 1.3.0
> * fsfs
> * FreeBSD 4.11
>
> The repository was dumped from host1 and loaded into a repository on
> host2. The dump/load completed without any errors, but the repository in
> host2 is now corrupt:
>
> output from repository on host1:
>
> $ svn cat -r 91056 file:///var/repos/roles/travel/db/expand
>
> $ svn cat -r 91057 file:///var/repos/roles/travel/db/expand
> db1.travel.dcn.yahoo.com
> db1.travel.mud.yahoo.com
> db1.travel.re3.yahoo.com
> db1.travel.scd.yahoo.com
> db1.travel.sp1.yahoo.com
> db2.travel.dcn.yahoo.com
> db2.travel.mud.yahoo.com
> db2.travel.re3.yahoo.com
> db2.travel.scd.yahoo.com
> db2.travel.sp1.yahoo.com
> db3.travel.dcn.yahoo.com
> db3.travel.mud.yahoo.com
> db3.travel.re3.yahoo.com
> db3.travel.scd.yahoo.com
> db3.travel.sp1.yahoo.com
>
> output from repository on host2:
>
> $ svn cat -r 91056 file:///var/repos/roles/travel/db/expand
> svn: Unable to find repository location for
> 'file:///var/repos/roles/travel/db/expand' in revision 91056
> $ svn cat -r 91057 file:///var/repos/roles/travel/db/expand
> svn: Invalid diff stream: [tgt] insn 0 starts beyond the target view
> position
>
> I've tried this on a backup copy of the repository and gotten the same
> results. Oddly enough, the checksums for the revs files on both host1
> and host are identical:
>
> host1:
>
> $ pwd
> /home/repos/db/revs
> $ md5 91056
> MD5 (91056) = ad90732659b5dfeab4c211bda28cd96d
> $ md5 91057
> MD5 (91057) = f5b0d431aac261ea9466bf6fcb15fb2b
> $ md5 91058
> MD5 (91058) = 468770bbbd202b92e0ff37d40be0f427
>
> host2:
>
> $ md5 91056
> MD5 (91056) = ad90732659b5dfeab4c211bda28cd96d
> $ md5 91057
> MD5 (91057) = f5b0d431aac261ea9466bf6fcb15fb2b
> $ md5 91058
> MD5 (91058) = 468770bbbd202b92e0ff37d40be0f427
>
> I've used svn dump/load without issue for 6-8 months now and haven't
> encountered anything like this. Can anyone offer any advice or
> assistance in getting to the root cause?
Is the problem reproducible (i.e. if you recreate the repository and
reload do you get the same problem)? Is it specific to that machine,
or can you make it happen on any system? Would it be possible to get
access to the dumpfile and/or the repositories for debugging purposes?
If not the entire thing, just the problematic revisions (both the
good and bad versions of them) would probably help.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 28 16:26:27 2006