You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by pe...@bigfoot.com on 2009/05/10 18:31:28 UTC
svnsync fails with cryptic message
I'm trying to do an initial svnsync of a 4Gb repository with 8500+
revisions, but it fails with the following error:
...
Committed revision 8410.
revision 8410
Copied properties for revision 8410.
property 8410
svnsync: Unable to fetch the node revision id of the version resource within the revision.
It leaves a lock and I need to propdel svn:sync-lock before I can try the
sync again, but the sync fails right away with the same error.
I've re-created the destination repo and re-tried the sync from the start
4 times and all 4 times it stopped just after the same revision (8410).
The Apache error log on the remote mirror shows this:
Could not CHECKOUT resource /path/to/repo/!svn/ver/8410/path/to/directory/in/repository. [409, #0]
Unable to fetch the node revision id of the version resource within the revision. [409, #160013]
The odd part is the path in the error message doesn't exist at revision
8410, it was added at revision 8411 (via a tag/copy).
I can checkout the entire repository (from the master) at revision 8410
and revision 8411 and it works fine in both cases.
I've run "svnadmin verify" on both the master and the mirror and there are
no errors on either side.
Is this a bug in 1.5.5? Or is the repository corrupted somehow that
isn't detectable by verify?
PS. Both systems are using subversion 1.5.5 and the destination (mirror)
repository is running apache 2.2.6. The repository type is fsfs on both
sides.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2174274
Re: svnsync fails with cryptic message
Posted by pe...@bigfoot.com.
On Thu, 21 May 2009, B Smith-Mannschott wrote:
> On Sun, May 10, 2009 at 20:31, <pe...@bigfoot.com> wrote:
>
>> [...]
>>
>> The Apache error log on the remote mirror shows this:
>>
>> Could not CHECKOUT resource /path/to/repo/!svn/ver/8410/path/to/directory/in/repository. [409, #0]
>> Unable to fetch the node revision id of the version resource within the revision. [409, #160013]
>>
>> The odd part is the path in the error message doesn't exist at revision
>> 8410, it was added at revision 8411 (via a tag/copy).
>>
>> [...]
>
> If you have the necessary access, could you check to see if you able to
> dump/load this repository successfully?
I was able to dump and load into a new repository without error.. All
svnadmin commands (dump, create, load) were done with 1.5.5. The
repository contains 9086 revisions and it's 3.7G. The dumpfile is about
7G.
> I ask because I have one repository which I am unable to dump/load
> cleanly because the dump file contains a few nodes in the wrong order
> (it tries to add files to a directory before adding the directory).
I assume svnadmin gave you some kind of error... either during the dump or
load?
Any other suggestions?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2352732
Re: svnsync fails with cryptic message
Posted by "B. Smith-Mannschott" <bs...@gmail.com>.
On Sun, May 10, 2009 at 20:31, <pe...@bigfoot.com> wrote:
> I'm trying to do an initial svnsync of a 4Gb repository with 8500+
> revisions, but it fails with the following error:
>
> ...
> Committed revision 8410.
> revision 8410
> Copied properties for revision 8410.
> property 8410
> svnsync: Unable to fetch the node revision id of the version resource within the revision.
>
> It leaves a lock and I need to propdel svn:sync-lock before I can try the
> sync again, but the sync fails right away with the same error.
>
> I've re-created the destination repo and re-tried the sync from the start
> 4 times and all 4 times it stopped just after the same revision (8410).
>
> The Apache error log on the remote mirror shows this:
>
> Could not CHECKOUT resource /path/to/repo/!svn/ver/8410/path/to/directory/in/repository. [409, #0]
> Unable to fetch the node revision id of the version resource within the revision. [409, #160013]
>
> The odd part is the path in the error message doesn't exist at revision
> 8410, it was added at revision 8411 (via a tag/copy).
>
> I can checkout the entire repository (from the master) at revision 8410
> and revision 8411 and it works fine in both cases.
>
> I've run "svnadmin verify" on both the master and the mirror and there are
> no errors on either side.
>
> Is this a bug in 1.5.5? Or is the repository corrupted somehow that
> isn't detectable by verify?
>
>
> PS. Both systems are using subversion 1.5.5 and the destination (mirror)
> repository is running apache 2.2.6. The repository type is fsfs on both
> sides.
If you have the necessary access, could you check to see if you able
to dump/load this repository successfully?
I ask because I have one repository which I am unable to dump/load
cleanly because the dump file contains a few nodes in the wrong order
(it tries to add files to a directory before adding the directory).
This very same repository is also impossible to sync without manual
intervention.
"Manual intervention", in my case, consists of:
- Check out the last successfully synced revision from TARGET
- Export the revision that fails to sync from SOURCE (this will be one
greater than the last successfully synced revision).
- Alter the working copy of TARGET so that it looks like the export of
SOURCE using something like svnemboss.sh
<http://svn.clifford.at/tools/trunk/svnemboss.sh>
- Commit the working copy of TARGET.
- Resume svnsync sync TARGET.
// Ben
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2342421