The current wording at:
http://subversion.tigris.org/faq.html#nfs
If you are using a repository with the Berkeley DB back end (default
for repositories created with Subversion 1.0 and 1.1, not the default
thereafter), do not access the repository via NFS. Berkeley DB does
not support storage of databases on remote file systems. Some NFS
servers claim that they explicitly support use of Berkeley DB on NFS-
mounted partitions, but we've only ever seen Berkeley DB databases
get corrupted when living on an NFS or SMB network drive.
Isn't quite correct.
Berkeley DB does support database and log file storage on NFS
filesystems, but Subversion cannot take advantage of that because at
least some Subversion commands ('svnadmin list-dblogs', 'svnadmin
list-unused-dblogs', 'svnadmin hotcopy') assume that databases and
log files are in the same directory as the Berkeley DB shared region
files.
As far as corruption goes, the only Berkeley DB corruption of which
I'm aware with respect to Subversion repositories was the corruption
caused by failure to run recovery appropriate on the databases, which
was fixed earlier this year.
I'd suggest the following wording:
If you are using a repository with the Berkeley DB back end (default
for repositories created with Subversion 1.0 and 1.1, not the default
thereafter), do not access the repository via NFS. Althought Berkeley
DB supports database storage on remote file systems, not all
Subversion functionality with be available in this configuration.
Thanks!
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
+1-781-259-3139
keithbosticim (ymsgid)
keith.bostic@oracle.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 29 21:28:03 2006