On 8/29/06, Danny Sung <dsung@lantronix.com> wrote:
>
>
> I'm looking into converting our CVS repository to Subversion. But I was
> wondering, since subversion stores the repository in a single Berkeley DB
> file, whether there is any size limitation to a repository. Our current CVS
> repository is about 1 TB. I know subversion will be much more space
> efficient, but at these sizes, I'm a little concerned. I couldn't find any
> reference in the FAQ or Book on this subject.
Since Subversion 1.2 or 1.3 FSFS is the default backend, so Berkeley DB is
not used by default, except if you specify the BDB backend when creating
the repository.
If you convert your existing CVS repository via cvs2svn you might not hit any
of the limits at all, assuming you don't have revisions in CVS which involve
a >2GiB commit. Just in case you want to make sure that no limit gets in your
way be sure to use Subversion 1.3.2 or newer linked against APR 1.2.x. If
you use mod_dav_svn this implies Apache 2.2. The APR sources bundled with
the Subversion tarball are APR(-Util) 0.9.x and don't support -DLARGEFILE
and this is the reason for the APR 1.2.x requirement.
> Also, I was wondering if anyone's used an SVN repository on ReiserFS. Are
> there any special issues or concerns with that? Is Reiser stable these
> days?
I'm using ext3 with -O sparse_super, dir_index and the default block-size is
ok. With a linked against APR 1.2.x svnserve I had no problem to import a
>5GiB source tree in one step as one changeset. This did of course not work
with svnserve linked against APR 0.9.x due to missing large file support.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 29 21:22:43 2006