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

Re: segfault on recover AND dump. is my repository doomed?

From: Seth Delackner <seth_at_jtan.com>
Date: 2003-04-17 20:21:38 CEST

On Thu, Apr 17, 2003 at 01:02:52PM -0500, Ben Collins-Sussman wrote:
> > I then used db 4.1 to load the files again, with no complaints.
> > Sadly, when I then try to checkout the repository, even after
> > svnadmin recover, it says the filesystem is corrupt.
> Was this on OS X or Linux?

OS X. I suppose I could try the load on Linux.
> > More generally, why is there no notice on the main tigris page
> > stating that OS X + DB 4.0.14 (you know, the version specified in
> > the INSTALL file) can destroy your data?
> Because nobody has ever seen that happen before.

The fun part is that I was not seeing any problems until someone on list told
me that 4.0 was dangerous in OS X, so I should migrate to 4.1. Of course, the
damage had already occured but was not visible because I was just checking IN,
never attempting to check OUT. I've been doing all these recovery attempts with
copies of my pre-migration 4.0-based repository.

> Can't you recreate the db files on linux with db_load?

Hrm. 1. db_dumped the db files using DB 4.0.14 on OS X. 2. created blank repository on linux (svn 20.1, db 4.0.14). 3. Tried to db_load, got lock and memory errors. 4. Deleted the new repository's db/* except for db/DB_CONFIG. 5. db_load successfully loaded the db files. 6. Ran svnadmin recover on the new repos, no errors. 7. Attempt to checkout the project in the repository:

svn: Invalid filesystem transaction name svn: no transaction named `5' in
filesystem `/root/svn2/db'

5 was the last repository revision in the old repository.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 17 20:22:31 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.