John Szakmeister wrote:
> On Wednesday 14 July 2004 14:18, Mitch Arends wrote:
>>>Mitch Arends <firstname.lastname@example.org> writes:
>>>>Yeah I tried the svnadmin recover command and even that hangs (there
>>>>are currently no other processes running against the repository). Not
>>>>sure what to with it at this point.
>>>You're positive you're executing 'svnlook' and 'svnadmin' as the same
>>>user/group that owns the repository, right?
>>Yes absolutely positive. I should have also mentioned that I'm running
>>subversion 1.0.4 on and Windows 2000 Server system.
>>The strange thing about the repository is that it's backup copy works
>>fine but the live production version of the repository didn't. There
>>also were no changes that were made b/n backup and the repository
>>becoming wedged so I'm no missing any key data. I just want to know why
>>and how to fix it.
> You could try to use the db_recover. The Windows version of the tools
> should be available at:
> You can use 'db_recover -vec -h /path/to/repos/db' to attempt a
> catastrophic recovery.
> I do have a couple of questions about how you're accessing the repository.
> What method are you using? By that I mean file://, svn://, or http://.
> Also, are you using TortioseSVN at all? The reason I ask is because I've
> seen one instance at work where somebody was using file:// access, and
> Explorer crashed while he was manipulating the repository. I don't think
> TortoiseSVN caused it, but it did have an ill effect on the repository.
> We've got him setup with svnserve now, which works great, and doesn't
> suffer from this sort of problem. :-)
We're using https:// to access the repository. We are also using only
TortoiseSVN exclusively to access the repository. I will try the
db_recover tool against the repository and let you know what I find out.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jul 15 16:12:33 2004