Justin Erenkrantz <justin@erenkrantz.com> writes:
> --On Monday, August 25, 2003 7:07 PM -0500 cmpilato@collab.net wrote:
>
> > That's really odd. Our filesystem code creates a new 'uuids' table if
> > that table isn't found.
>
> Well, that's what I thought, too. r4392 can dump it, but r6590 can't
> (and intermediate versions we had installed - 5613, 6109 - also fail).
>
> Here's what I get:
>
> % /usr/local/svn-install/svn-r6590/bin/svnadmin dump wiki.old
> SVN-fs-dump-format-version: 2
>
> svn: Berkeley DB error
> svn: Berkeley DB error while get repository uuid for filesystem wiki.old/db:
> DB_NOTFOUND: No matching key/data pair found
> % /usr/local/bin/db4_dump -h wiki.old/db uuids
> VERSION=3
> format=bytevalue
> type=recno
> re_len=36
> HEADER=END
> DATA=END
>
> No data there. FWIW, the new repository has:
>
> % /usr/local/bin/db4_dump -h wiki/db uuids
> VERSION=3
> format=bytevalue
> type=recno
> re_len=36
> HEADER=END
> 39646133336438302d616363352d303331302d386630642d663161656233656463366432
> DATA=END
>
> HTH. So, I think we created a new UUID when we imported.
>
> Let me know if there's anything else I can provide. But, boy, am I
> glad we kept really old versions around.
This is insane. It is absolutely not how the Subversion code was
written to work, and not how it behaves for me. I mean, I can
repeatedly remove the uuids table from my repository, run 'svnadmin
dump', and get no error. See how the UUID gets generated anew each
time?
$ svnadmin dump foo | grep UUID
* Dumped revision 0.
* Dumped revision 1.
UUID: 5cfd6d54-c4c5-0310-808f-d49363ad8054
$ rm foo/db/uuids
$ svnadmin dump foo | grep UUID
* Dumped revision 0.
* Dumped revision 1.
UUID: c91fa557-c4c5-0310-b62f-bff0f61c59a0
$ rm foo/db/uuids
$ svnadmin dump foo | grep UUID
* Dumped revision 0.
* Dumped revision 1.
UUID: 1503d457-c4c5-0310-9fd6-e38dcf03b400
$ rm foo/db/uuids
$ svnadmin dump foo | grep UUID
* Dumped revision 0.
* Dumped revision 1.
UUID: 16592958-c4c5-0310-a78e-b35be8769eea
What happens if you 'mv db/uuids db/was-uuids' before trying a dump
of your old database with new(er) Subversion code (0.27.0, say) ?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 26 06:36:40 2003