mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2014-05-17 17:00:20 +00:00 committed by admin
parent 215d00a267
commit 1917b0e3ef
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/forum/Distributing_data_to_a_set_of_drives/comment_2_e13b4e5c1e6f1f503f93d521b504d5c1._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="216.145.95.162"
subject="comment 2"
date="2014-05-17T17:00:19Z"
content="""
git-annex doesn't allow bonding repositories like that, but it does have repository groups which can accomplish the same thing.
For example, if you put B C and D into the archive group, and set the [[preferred_content]] expression to \"standard\", then each repository will only want files that have not yet reached some other archive repository.
Or, you can make up your own group name, like \"BCD\" and set the preferred content of each repository to something like \"not (copies=BCD:2)\" -- and now it will try to have 2 copies of each file on one of the drives.
Once it's configured, using either the git-annex assistant, or `git annex sync --content` will copy files around according to the configuration.
This will tend to fill up the first drive, or the first 2 drives, and only use subsequent drives if files don't fit on the first drive. You can use [[cost]] settings to control which drives files are put on.
"""]]