[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: the 0.24 release?

From: Jamin W. Collins <jcollins_at_asgardsrealm.net>
Date: 2003-06-11 23:38:26 CEST

On Wed, Jun 11, 2003 at 02:35:21PM -0700, Greg Stein wrote:
> On Wed, Jun 11, 2003 at 02:09:29PM -0700, Blair Zajac wrote:
> > Where have you been :) There have been reports of svn/BDB 4.1.25
> > repositories getting corrupted probably once a month or so.
> >
> > Collab.net was going to put somebody onto tracking down this issue
> > but that hasn't happened yet.
> Eh? Is this the one that is generally typified by people using
> multiple access paths, and then you need to run recovery every now and
> then?

Nope, not in my case. Single access path, and more or less single user.
It's a personal system I have here in the house for myself and my wife.
We have a few repositories on it for different things. TMK, I was the
only one accessing the system at all that day.

> When I see the word "corruption", I think "data loss." Rather than
> "BDB is freaked out. Give it a 'lude."

There was data loss, complete and utter. The repos was (and still is
AFAIK) completely uncoverable. Luckily it was a repository that I was
using mainly to track changes another developer was making, and I was
able to retrieve periodic sources from him to recreate the repository
manually. So, I have the repository back, but not exactly as it was.
To me, that constitutes "data loss".

Would a dump of the database worked? Yea. However, for that to work, I
would have to have a hook that dumped the repos after each and every
successful commit, which I don't.

Jamin W. Collins
Remember, root always has a loaded gun.  Don't run around with it unless
you absolutely need it. -- Vineet Kumar
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 11 23:39:22 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.