[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: no transaction named `4v' in filesystem

From: Roland Bramm <roland_at_butlers-djihad.de>
Date: 2003-05-08 11:38:48 CEST

At 23:25 Uhr -0500 07.05.2003, kfogel@collab.net wrote:

>Wow. I'm sorry, I have no idea what to say.

Shit ;-)

>I don't know why fink thinks the client depends on bdb 4.1; we're
>still "officially" 4.0.14, though 4.1 should work too. But your
>repository was created with 4.0.14, presumably... hmm.

There were some rumors that the db 4.0.14 caused some repositorys to
be corrupted on MacosX (maybe my error is also related to this ...)
so the packager of the svn-client package changed the dependency to
db41.

>Next time, I'd recommend recording all the error messages you get, if
>possible. And, when you get a repository recovered, if you're at all
>worried, the first thing you should do is 'svnadmin dump', not
>'svnadmin rmtxns' :-).

Thanks, i completly "forgot" the dump ....
i could recover the whole repository via the dump load (so into a new
one) without the last 2 commits. This is no problem, because my
working copy still has all which is needed to get these.

The only strange thing is that i updated the svn client in rev 113
and from there on i couldn't ci somthing new, but during the
svnadmin dump /Volumes/Files/Subversion/ > repos.dump
everithing works fine until:
* Dumped revision 111.
svn: Invalid filesystem transaction name
svn: no transaction named `4u' in filesystem `/Volumes/Files/Subversion/db'

and this is before the update ??!

But anyway now everything is fine, the next time i do it with more caution :-)

Thanks
Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 11:42:16 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.