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

extremely wedged repository

From: Karan, Cem \(Civ, ARL/CISD\) <CKaran_at_arl.army.mil>
Date: 2004-11-01 21:05:33 CET

I've managed to wedge my repository to the point that I can't get
svnadmin recover to work, and the Berkley tools segfault just trying to
work on it. Here are the specs of what I've got, and what is wedged:
 
Running on Mac OS X 10.3.5 with all of the latest patches (last patch
update was 28 Oct 2004, which was the latest release).
 
Using Subversion 1.0.9 (r11378) as installed by fink
(http://fink.sourceforge.net)
 
When I try to use 'time svn recover', it claims that the recovery is
complete, and that the latest revision is 10 (which makes sense) but it
does the entire recovery in 0.140 seconds of user time; I'll admit, I
only have a couple hundred files, but that is a bit fast.
 
When I do 'db_recover -c', I get the following:
db_recover: DB_LOGC->get: LSN 13/843898: invalid log record header
Segmentation fault
 
When I go to my project directory, and run svn cleanup, everything seems
OK.
 
But when I try to commit, I always get the following:
 
Sending (a source file)
Adding (another source file)
Abort Trap
 
There are only 2 other possible oddities in how I set up my directories:
1) I do use spaces in some of my names (E.g., I may have a path like
"foo/baz/bar bar") but this doesn't seem to have thrown it before.
2) I'm running everything off of an encrypted disk image; I've checked
to make sure that there is enough room to do the commits, and there is.
Also, there didn't seem to be any problems before.
 
Any suggestions? Also, if this is going to a mailing list, I'm not part
of the list; you'll have to mail me directly.
 
Thanks,
Cem Karan
Received on Mon Nov 1 21:17:23 2004

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