John,
Thanks for the reply. Hmmm. Yes, it does seem as if something weird has
happened with my filesystem over-all. Yes, I do have a backup, and,
fortunately, the working copies of the repository are all intact.
It looks like I have db4 4.2.52_0 (according to "port installed" from
Darwinports).
Thanks for the suggestion about fsfs, I'll do that, and migrate my up
to date working copy into a new repository.
Now I am starting to understand some of the subtlety of project layout.
My other broken repository holds a large piece of code with many
subdirectories. The code in the subdirectories is subversioned, but the
data files in the subdirectories is not. It is going to be a pain to
move the data (or tell subversion to ignore it) to recreate the
repository. Any suggestions?
Regards,
Ed
On Monday 14 March 2005 00:29, Ed Zaron wrote:
> Hi Everybody,
>
> I have been using subversion for a while (6 mo.) to manage two
> repositories. Recently I updated and started using https access. I
> thought everything was going well, and then ...
>
> Symptom #1 : I issue the command from one of my working copies on a
> remote machine
> svn commit -m "test"
> and no message is returned to standard out, i.e., nothing seems to
> happen. (And the apache2 logs don't indicate any request.)
>
> Symptom #2: I issue the same command from the local machine and I get
> the message:
> Sending user_doc.txt
> svn: Commit failed (details follow):
> svn: PROPFIND request failed on '/svn/Tako2/!svn/vcc/default'
> svn:
> Reference to non-existent revision 17 in filesystem
> '/Users/Shared/svn/Tako2/db'
>
> I have tried using svnadmin dump and svnadmin load to create a fresh
> repository (followed by svn switch --relocate), but the same error
> message appears. I have also tried svnadmin recover, and that reports:
>
> ezaron% sudo -u www svnadmin recover /Users/Shared/svn/Tako2
> Password:
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 8.
Here's the problem. The repository thinks it only has 8 revisions in
it,
while your working copy has 17. It looks to me like you may have lost
some data (do you have a backup?).
I do have a couple of questions for you though. You appear to be using
BDB as your backend. Which version? The 4.1.x line and earlier had a
series of problems on MacOS X. However, given all the problems that
I've
seen in the past with MacOS X and BDB, I'd suggest you avoid BDB
entirely, and use the FSFS backend ('svnadmin create --fs-type fsfs').
It uses basic file system properties to create transactions, and provide
the required atomicity.
-John
..............................................
Edward D. Zaron, PhD
Research Associate
College of Oceanic and Atmospheric Sciences
Oregon State University
Corvallis, OR 97331-5503
Phone: (541) 737-3504
Fax: (541) 737-2064
ezaron@coas.oregonstate.edu
...............................................
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 14 19:26:22 2005