Berkeley DB error while opening changes table, invalid argument

Hello,

I looked through the open issues, and didn't see anything about this. I'm
hoping someone has some advice for me.

We had a working copy with some binary files in it. Did "svn rm" then "svn
ci" to get rid of some of them. Then, on my working copy, I did an "svn up"
and the files didn't go away. "Odd" I said. They appeared in the browser
when I went to that directory in the repository, yet on this one working
copy, they weren't there. On my working copy, I did "svn rm" then "svn ci"
on these annoyingly persistent files, and they went away. Back to the other
working copy, did "svn up", and I got a bunch of messages that these
non-existant files were deleted!

At this point, subversion is down. All I get now are Berkeley Database
errors. For example:

Berkeley DB error while opening 'changes' table for filesystem
myproj/repos/db: Invalid Argument

I did a hot-backup on Monday, so I don't think we've lost too much, but I'd
rather not have to resort to that. Any ideas?

--- Eric

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 13 18:36:17 2003