You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Martin Zdila <m....@mwaysolutions.com> on 2009/05/04 07:22:45 UTC

Re: can't recover svn repository

hello.

as nobody can answer, should I raise a bug in the issuetrack?

thanks in advance
br

On Thursday 30 April 2009 17:59:20 you wrote:
> Hello
>
> start:
>
> $ svn log svn://myserver/myproject
> svn: Reference to non-existent node '2mnj.2db.814' in filesystem
> '/var/svn/repos/db'
>
> $ svnadmin verify -r 9699 /var/svn/repos
> svnadmin: Reference to non-existent node '2mnj.2db.814' in filesystem
> '/var/svn/repos/db'
>
> $ svnadmin recover /var/svn/repos
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 12171.
>
> goto start;
>
>
> I am using subversion 1.5.6 as debian package and db4.6 as a backend. Any
> hint how to fix it?
>
> Thanks in advance
> Bestregards

-- 
Martin Zdila 
CTO

M-Way Solutions Slovakia s.r.o.
Letna 27, 040 01 Kosice
Slovakia

tel:+421-908-363-848
mailto:m.zdila@mwaysolutions.com
http://www.mwaysolutions.com
xmpp:zdila@jabbim.sk (Jabber)
skype:m.zdila

Re: can't recover svn repository

Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 4, 2009, at 02:22, Martin Zdila wrote:

> On Thursday 30 April 2009 17:59:20 you wrote:
>
>> $ svn log svn://myserver/myproject
>> svn: Reference to non-existent node '2mnj.2db.814' in filesystem
>> '/var/svn/repos/db'
>>
>> $ svnadmin verify -r 9699 /var/svn/repos
>> svnadmin: Reference to non-existent node '2mnj.2db.814' in filesystem
>> '/var/svn/repos/db'
>>
>> $ svnadmin recover /var/svn/repos
>> Repository lock acquired.
>> Please wait; recovering the repository may take some time...
>>
>> Recovery completed.
>> The latest repos revision is 12171.
>>
>> goto start;
>>
>>
>> I am using subversion 1.5.6 as debian package and db4.6 as a  
>> backend. Any
>> hint how to fix it?
>
> as nobody can answer, should I raise a bug in the issuetrack?

No, you should not file a bug in the issue tracker, unless someone  
here confirms that this is a bug. This policy is explained on the  
issue tracker page.

It sounds to me more like a corrupt repository than an outright bug.

In case it is a bug, I recommend you try the latest version of  
Subversion, 1.6.1, to see if the issue persists.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2061106

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].