On Tuesday 13 January 2004 13:18, Roland Bramm wrote:
> >On Monday 12 January 2004 07:12, Roland Bramm wrote:
> > > Hi,
> >>
> >> today a strange thing happend using svn ...
> >>
> >> today i tried to check in my changes and got
> >> svn: Invalid filesystem revision number
> >> svn: svn_repos_get_logs: No such revision '263'
> >>
> >> but in the svn keywords in the file there is:
> >> * @version $LastChangedRevision: 263 $
> >> * @date $LastChangedDate: 2004-01-09 18:12:26 +0100 (Fri, 09
> >> Jan 2004) $
> >>
> >> then i did a svnadmin recover
> >>
> >> which leads to
> >> admin recover /Volumes/Files/Subversion/
> >> Acquiring exclusive lock on repository db.
> >> Recovery is running, please stand by...
> >> Recovery completed.
> >> The latest repos revision is 263.
> >>
> >> so it seems that "everything is back to normal".
> >>
> >> but if i now try to do "something"
> >> i get:
> >> svn log Calculations.C
> >>
> >> svn: Invalid filesystem transaction name
> >> svn: no transaction named '7k' in filesystem
> >> '/Volumes/Files/Subversion/db'
> >>
> >> also for svn up , ...
> >
> >Oof, that's no good. This sounds like a problem in the database. In
> > other words, it sounds like something got horked here. Did you run
> > 'svnadmin recover' while Apache was up?
>
> No Apache was down (or at least the apache with the svn_dav module,
> the standard Apple apache 1.3 was up but only for simple html
> pourpose) and the recover didnt quote an error.
Good.
> Acquiring exclusive lock on repository db.
> Recovery is running, please stand by...
> Recovery completed.
> The latest repos revision is 263.
Interesting. If that completed okay, then that leads me to believe that it
was okay after running recover.
> > Does 'svnadmin verify' complete successfully
> >on the repository?
>
> no it ends:
> * Verified revision 261.
> * Verified revision 262.
> svn: Invalid filesystem transaction name
> svn: no transaction named '7k' in filesystem '/Volumes/Files/Subversion/db'
Yeah, this isn't good. I'm not sure how to recover from this problem (my
experience with the db tools is pretty limited). If you can dump r0-r262,
then I'd say do that and pull your latest changes from the working copy.
> > > i am using the latest fink version
> >>
> >> svn --version
> >> svn, version 0.33.1 (r7789)
> >> (hmm interesting quite old .....but there is no newer in fink ...)
> >
> >I know I've seen several things regarding svn for Mac OS X. I believe
> > David Summers got fed up with fink, and I think has some binary Mac OS X
> > on his site. Check it out at:
> >
> >http://summersoft.fay.ar.us/pub/subversion/i386/subversion-latest/macosx/
>
> Thanks
> when the repos works again i will install the new version ...
>
> > > how can i remove a "invisible" transaction ?
> >
> >The problem is that you have an invisible transaction, it's that one named
> >'7k' doesn't exist.
> >
> >Can you say what you did that led up to this problem? If there is a bug,
> > it may help us to track down this problem.
>
> yes and no ...
> there was no "strange" thing what i did, this problem popped up.
> The checkin of revision 263 was working properly ...
> than i only have some scripts which access svn log "File" to put the
> output in the doxygen documentation.
> The error appeared when i tried to checking somthing new ...
> The only "special" thing what happened was a power shortcut but
> during this time there was absolutly no access done to svn. (this
> happened in the night and i dont have any cron job, running script or
> whatsoever accessing svn ...)
>
> are there some logs in the db or somwhere else which could help ?
Unfortunately, I'm no guru with the db tools... perhaps someone else here on
the list can chime in with some recommendations.
> How can i get into work again ?
> the dump of the repos is working up to 262 ... so i could just
> rebuild the complete repoos with this dump and checkin the 263
> changes again (there were not to much changes done) or is there
> another way ?
I would say to the dump and check in your r263 changes again. Keep track of
what you're doing when checking in the r263 changes, just in case it gets
corrupted again.
Sorry I couldn't help more.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 14 02:05:58 2004