Home/ Questions/Q 550799
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T11:19:36+00:00

I dumped my repository svnadmin dump repos > repos.dump then I loaded it on

  • 0

I dumped my repository

svnadmin dump repos > repos.dump

then I loaded it on the new machine

svnadmin load newrepos < repos.dump

and when finished the new repository is missing the last few hundred revisions.

Can I inspect repos.dump to see if it is missing the revisions? Can I dump the missing revisions and load them onto the new repository? Or, do I have to start over from scratch.

Starting from scratch would be a pain since the repository is 3GB and I have to grab it across the Internet at moderately low speeds!

EDIT: SOLVED – OPERATOR ERROR!

So, I forgot that I had already migrated the repository once (from account1 to account2) and and I never removed the account1 repository. I have a bash function to quickly ssh into my remote accounts and it logs me into account1 by default (which I wasn’t thinking about) and since I saw the repository I figured everything was fine and hence sent the dump to account3 (again using an alias so that I didn’t notice that I was in the wrong account).

Now, I’m going about putting the username for the account in bright red in the terminal, and I’m caching old repositories rather than letting them lie around. And, I’m taking out the default user aspect of my profile hack.

But, I was able to use --incremental to transfer the missing revisions to the new location. So, all the advice still helped.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would guess that your dump is larger than 4 GB (as dumps aren’t saved with deltas by default, so they may be much bigger than the repo), and some step of the process of transferring the dump truncated to 4 GB, which is the maximum file size on some filesystems (and possibly in some protocols as well). It’s also possible that some step of the process could be truncating it at 2 GB, depending on the file transfer method you’re using.

    You can check by inspecting the file; it should have revision numbers in it, and you can see how high they go.

    Instead of starting the whole process over again, you can use the --incremental option to svnadmin dump to produce an incremental dump, starting with the last good revision you loaded into the new repo. Loading an incremental dump into an existing repository should work fine. You would do something like

    svnadmin dump --incremental -r 1234:HEAD > repos.2.dump
# Transfer to new system
svnadmin load < repos.2.dump
    • 0