Ryan Schmidt wrote:
> On May 16, 2006, at 18:07, Nico Kadel-Garcia wrote:
>
>>> What should I do when the disk that SVN is on is nearly full ?
>>>
>>> I know I can migrate my repositories to a bigger disk. But is it
>>> also possible to :
>>>
>>> 1. Move some repositories to NFS partitions
>>> 2. Obliterate old file copies from some repositories ?
>>
>> It's often possible to throw out a lot of old debris, by creating a
>> duplicate of the repository that is much smaller. But for various
>> reasons, NFS is a bad idea for Subversion repositories:
>>
>> Look into the "svndumpfilter" tool for doing duplications of a
>> repositories contents, with careful use of the "exclude" option.
>> But "old file copies" is usually a misnomer: if the fle exists in
>> *any* active branch, or is a base file for difference-recorded
>> copies of the file, you don't gain much by trying to eliminate
>> other copies of the file because Subversion uses a database, not
>> merely copies of the file.
>
> If your repository is FSFS (which IMHO it should be) you can move old
> revision files off to a second drive and symlink them back into place
> if you like.
>
> As far as I know, NFS breaks BDB repositories but isn't a problem for
> FSFS repositories.
>
> If you need to convert your repository from BDB to FSFS, instructions
> are in the FAQ on the web site.
If he's running out of disk space as it is, he may have some difficulty
finding a place to migrate it to. And there's a potentially big performance
hit for using something like NFS instead of local disk. Given the low cost
of modern SATA nad high-speed IDE drives, there's little reason to use NFS
for something like thus unless you need some sort of weird
high-avaialability network appliance setup.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 16 20:43:12 2006