restore error svnadmin: E160013: File not found
MOKRANI Rachid
Hi,
I am trying to migrate a SVN Project without success. I have a lot errors like E160013…..
Any idea help will be very appreciated
Following all I done on CentOS platform.
1. The source project has a size of 60GB and 170 000 revisions installed on a SVN server, Version 1.6.12 (r955767)
Some revisions are missing (I do not know why ...) in the source project and to perform the dump I execute the following script. The dump takes 4 hours.
#! / bin / bash
$ svnadmin dump $old_repo -r1> $save_path/r1.dump
for rev in `seq 170000` 2; do # 170000 is the number of the last revision
echo $rev
$ svnadmin dump $old_repo -r$rev --incremental > $save_path/r${rev}.dump
done
The dump goes well and when it is finish (4 hours later) I get a directory of size 170GB (du -sh $save_path)
2. Then on the new SVN server, Version 1.8.11 (r1643975) I do a restore with this script. The restore ends after 25 hours.
svnadmin create $new_repo
$ svnadmin load $new_repo < $save_path/r1.dump
for rev in `seq 162717` 2; do
echo $rev
$ svnadmin load $new_repo < $path_path/r${rev}.dump
done
This is where the problem begin ....
I get to very very many messages with the error below.
svnadmin: E160013: File not found: transaction '113292-3h08' path .......
....
....
svnadmin: E160013: File not found: transaction '113292-3h0a' path '...
....
svnadmin: E160013: File not found: 113267 revision, path ....
....
….
When the restore finish, a lot of files are missing and the result du –sh $save_path return ONLY 25GB
Help please.
__________________________
Avant d'imprimer, pensez à l'environnement ! Please consider the environment before printing !
Ce message et toutes ses pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. IFP Energies nouvelles décline toute responsabilité au titre de ce message. This message and any attachments are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. IFP Energies nouvelles should not be liable for this message.
__________________________
Andreas Stieger
> svnadmin create $new_repo
> $ svnadmin load $new_repo < $save_path/r1.dump
> for rev in `seq 162717` 2; do
> echo $rev
> $ svnadmin load $new_repo < $path_path/r${rev}.dump
> done
Andreas
MOKRANI Rachid
After reading the URL below, this is the only way I've found to do a complete dump of my repo with a lot of missing revisions
http://stackoverflow.com/questions/15474513/svn-fix-or-remove-broken-revisions
http://www.wandisco.com/svnforum/forum/opensource-subversion-forums/general-setup-and-troubleshooting/5377-missing-revisions-problem-svnadmin-dump
Regards.
-----Message d'origine-----
De : Andreas Stieger [mailto:Andreas...@gmx.de]
Envoyé : vendredi 27 novembre 2015 13:09
À : MOKRANI Rachid
Cc : us...@subversion.apache.org
Objet : Re: restore error svnadmin: E160013: File not found
Nico Kadel-Garcia
> Hi,
>
> After reading the URL below, this is the only way I've found to do a complete dump of my repo with a lot of missing revisions
>
> http://stackoverflow.com/questions/15474513/svn-fix-or-remove-broken-revisions
> http://www.wandisco.com/svnforum/forum/opensource-subversion-forums/general-setup-and-troubleshooting/5377-missing-revisions-problem-svnadmin-dump
>
>
> Regards.
copy of both stdout and stderr to in a local record, in case of missed
errors.
There is also a point, when you're doing things like discarding
revisions, that you need to consider "do I want to keep this whole
thing and ofrce people to reload all their working copies, to skip the
discarded revisions correctly? Sometimes, when people have committed
bulky and unnecessary binaries or re-arranged and re-arranged the
structure, or when there's a lot of broken old code or code with
embedded plaintext passwords, that you can reasonable say "just export
the specific working directories to a new repository, with no history,
and add a README that says where the old repository is".
MOKRANI Rachid
this is a good approach to replace svnadmin dump / load by hotcopy? I have never done that.
On the server with svn 1.6 release I'll be able to
$ svnadmin hotcopy my_repo /tmp/my_repo_copy
and after moving the copy from my old server /tmp /my_repo_copy to the new SVN server with version 1.8
Is this a good approach?
-----Message d'origine-----
De : Nico Kadel-Garcia [mailto:nka...@gmail.com]
Envoyé : vendredi 27 novembre 2015 14:35
À : MOKRANI Rachid
Cc : Andreas Stieger; us...@subversion.apache.org
MOKRANI Rachid
And on the new server with SVN release 1.8 I need to do :
svn upgrade my_hotcopy_repo
Is it a good approach ? (actually dump/load is not working for me)
Many thanks.
-----Message d'origine-----
De : MOKRANI Rachid
Envoyé : vendredi 27 novembre 2015 15:21
À : us...@subversion.apache.org
Objet : RE: restore error svnadmin: E160013: File not found
Thanks for your answer.
this is a good approach to replace svnadmin dump / load by hotcopy? I have never done that.
On the server with svn 1.6 release I'll be able to $ svnadmin hotcopy my_repo /tmp/my_repo_copy
and after moving the copy from my old server /tmp /my_repo_copy to the new SVN server with version 1.8
Is this a good approach?
-----Message d'origine-----
On Fri, Nov 27, 2015 at 7:59 AM, MOKRANI Rachid <rachid....@ifpen.fr> wrote:
> Hi,
>
> After reading the URL below, this is the only way I've found to do a
> complete dump of my repo with a lot of missing revisions
>
> evisions
> http://www.wandisco.com/svnforum/forum/opensource-subversion-forums/ge
> neral-setup-and-troubleshooting/5377-missing-revisions-problem-svnadmi
> n-dump
>
>
Those look like useful scripts. I'd run them with a "nohup" to keep a copy of both stdout and stderr to in a local record, in case of missed errors.
There is also a point, when you're doing things like discarding revisions, that you need to consider "do I want to keep this whole thing and ofrce people to reload all their working copies, to skip the discarded revisions correctly? Sometimes, when people have committed bulky and unnecessary binaries or re-arranged and re-arranged the structure, or when there's a lot of broken old code or code with embedded plaintext passwords, that you can reasonable say "just export the specific working directories to a new repository, with no history, and add a README that says where the old repository is".
Philip Martin
> Oups...i think i need to do an upgrade.
>
> And on the new server with SVN release 1.8 I need to do :
>
> svn upgrade my_hotcopy_repo
>
> Is it a good approach ? (actually dump/load is not working for me)
http://subversion.apache.org/docs/release-notes/1.8.html#compatibility
"There is no need to dump and reload your repositories. Subversion 1.8
servers can read and write to repositories created by earlier versions"
However your repository is corrupt and it is hard to predict exactly
what will work and what will fail.
--
Philip Martin
WANdisco
Nico Kadel-Garcia
better chance of being able to dump and reload and upgrade from that
revision. There can be differences between "bad revision that can't be
salvaged with an up-to-date software version", and "confusing revision
that svnadmn dump is having trouble dumping cleanly".