Yes I tried svnrecover. It doesn't output anything after "Please wait;
recovering the repository may take some time...". I let it run for almost
40 minutes (I disabled one cpu, now it's a single P3 600 Mhz, operating on a
70 Mb repository), and the cpu is used at 0%. All the svn command freezes
and don't complete (I've shut down apache and that's the only way the users
got there so I'm sure to be the only one accessing it).
It's probably not even a direct svn bug but it sounds to me like the
berkeley db is in a bad shape, and the cause is potentially the same that
this user below experienced: dual cpus and/or raid.
-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, May 24, 2004 12:46
To: Brice Dardel
Cc: users@subversion.tigris.org
Subject: RE: Berkeley DB error + svnadmin freezes
On Mon, 2004-05-24 at 12:42, Brice Dardel wrote:
> I just encountered the same error as described by Stefan below. I have a
> few repositories on the machine, one of them when I do a "svnadmin verify"
> does:
>
> svn: Berkeley DB error while opening 'revisions' table for filesystem
> marketing/
> db:
> Not enough space
Did you run 'svnadmin recover'?
'svnadmin verify' is equivalent to checking out (reading) every single
revision. If other read-operations fail, so will 'verify'.
I'm seeing a general trend: a lot of users seem to think 'verify' means
'read and repair'. It doesn't. It just means 'read'. Only the
'svnadmin recover' command does any repair.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 24 20:19:56 2004