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

Re: subversion 1.1.0 checkin crashes - repo needs recovery

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-10-20 15:59:47 CEST

Martin MAURER wrote:

> I am using version 1.1.0 with a bdb backend.
> access method file://
> Recently when i tried to check in some changes i got a crash.
> backtrace follows:

Just to clear up a few things before anyone else can dive deeper:

1) file:// access is primarily useful for single user access; if
multiple uid's need access to the repository you are much more likely to
have problems with setting the ownership and umask correctly. svnserve
is much easier to manage correctly and can be bound to the loopback
address for additional security.

2) Just to confirm, BDB files cannot be accessed safely on any networked
harddrive (e.g. NFS, SAMBA, NT mounts) because of the way that BDB
manages shared access using a memory mapped region. This is not a
limitation of FSFS repositories (though there are issues with large
repository under NTFS, due to the number of files created).

3) You need to tell us the OS and other information about your environment.

4) After checking to see that the file ownership is consistent
(especially that the log files must be r/w by the user accessing the
repository, and preferrably owned by that user), did you run

        svnadmin recover REPOS_PATH

and what did it say?

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 20 15:59:58 2004

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.