You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Marcus Mikolaiczyk <ma...@carmedialab.de> on 2005/08/01 12:28:54 UTC
Various Dump Sizes
Hi all,
I got a behaviour of the command
svnadmin dump myrepos > dumpfile
which i cannot explain myself. So let's start at the beginning.
Using SVN 1.1 with Berkeley DB. I got a repository with 520 revisions.
Revision 0-420 are emty ones and the rest contains data - but this
should have no impact on the dumps. Sizes are in Kbytes.
The Berkeley DB Rpository:
265780 /svn/repository/TestMiko
Full dump :
svnadmin dump /svn/repository/TestMiko > TestMiko.dmp
267240 TestMiko.dmp
Partial Dump from Revision 510 to 520:
svnadmin dump /svn/repository/TestMiko --revision 510:520 >
TestMiko_510-520.dmp
798964 TestMiko_510-520.dmp
As one can see the Dumpsize for the full dump is slightly larger than
the real repos size. But dumping revision 510-520 produces a file which
is almost three times larger than the repos or the full dump.
I got no error during the dumps an the dump begins with :
svn@ra:/tmp> head TestMiko*
==> TestMiko.dmp <==
SVN-fs-dump-format-version: 2
UUID: 4af0156d-9fde-0310-881f-e7f1d550fd13
Revision-number: 0
Prop-content-length: 56
Content-length: 56
K 8
svn:date
.......
==> TestMiko_510-520.dmp <==
SVN-fs-dump-format-version: 2
UUID: 4af0156d-9fde-0310-881f-e7f1d550fd13
Revision-number: 510
Prop-content-length: 126
Content-length: 126
K 7
svn:log
.......
I know that it has to generate a head revision when dumping a range of
revisions but I cannot explain why the result should be larger that a
full dump.
Anyone an idea/explanation?
Kind Regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org