Sorry for disturbing you folks,
I took my time and read the svnbook another time, and found an
interesting warning :
"Do not create a Berkeley DB repository on a network share—it cannot
exist on a remote filesystem such as NFS, AFS, or Windows SMB. Berkeley
DB requires that the underlying filesystem implement strict POSIX
locking semantics, and more importantly, the ability to map files
directly into process memory. Almost no network filesystems provide
these features. If you attempt to use Berkeley DB on a network share,
the results are unpredictable—you may see mysterious errors right away,
or it may be months before you discover that your repository database is
subtly corrupted."
"If you need multiple computers to access the repository, you create an
FSFS repository on the network share, not a Berkeley DB repository. Or
better yet, set up a real server process (such as Apache or svnserve),
store the repository on a local filesystem which the server can access,
and make the repository available over a network. Chapter 6, Server
Configuration covers this process in detail."
I though that since I wasn't using BDB, but FSFS, this won't affect me,
but I still tried to create a repository on a local filesystem, and
guess what, it worked !
[ny@localhost tmp]$ svnadmin create --fs-type fsfs repos
[ny@localhost tmp]$ svnadmin verify repos
* Verified revision 0.
[ny@localhost tmp]$ svnlook info repos
2005-10-28 21:59:02 +0200 (Fri, 28 Oct 2005)
0
Now, I'm quite sure that the svn I'm using hasn't been compiled with
FSFS support, but I wonder how I could know about that.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 28 22:06:48 2005