26 jun 2006 kl. 04.41 skrev Bryan D. Andrews:
> We have a problem where somehow something was corrupted on a commit
> in a
> new directory added.
>
> We cannot do a complete dump now as it chokes on that revision:
> svnadmin: Can't read length line in file 'c:\svn\AppTheory\db\revs
> \2445'
>
> We cannot update from that directory either:
>
> Error: REPORT request failed on '/projects/!svn/vcc/default'
> Error: REPORT of '/projects/!svn/vcc/default': 200 OK (http://
> myserver)
>
>
> 3 questions:
>
> 1. we have had approximately 10 commits since then and I need to know
> the best way to deal with situations like this.
>
> 2. what is the best way to automatically backup in the windows
> environment. I do full dumps each night but now I am not sure of the
> integrity -- it still creates the dump files even though the dump did
> not complete successfully. I have heard that it returns codes but I am
> not sure how to retrieve them in my script.
>
> 3. Are their commercial products to help manage SVN and SVN backups?
>
> Any help is appreciated.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
Is your Repository stored as FSFS or as a Berkley DB?
The book 'Version Control with Subversion' is quite clear about one
thing:
Berkley DB:s should be stored only on disks connected directly to the
server,
and never on any network share. All existing network shares lacks
essential locking
for this to work.
------------------------------------------------------
"Home is not where you are born, but where your heart finds peace" -
Tommy Nordgren, "The dying old crone"
tommy.nordgren@chello.se
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 26 20:05:29 2006