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

Browse source
This commit is contained in:
MatusGoljer 2018-03-25 14:48:57 +00:00 • committed by admin
parent a6f8d9ab28
commit 108068a8a2
1 changed files with 31 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
doc/forum/what_rules_is_git_annex_sync_--content_using_to_send_files_out.mdwn Normal file
View file

@ -0,0 +1,31 @@
I have two regular git clones and 4 special remotes (cloud
storage mostly).
My `numcopies` is set to 2 which means I always need to have at
least two copies. One usually lives in one of my git clones
which is a backup and so has everything. The other is somewhere
in the cloud.
When I add a new file to my client clone and do `git annex sync
--content` is this respecting the prefered content of each remote
or is it only trying to satisfy the numcopy?
These are my settings for archive and smallarchive
groupwanted smallarchive = ((include=*/archive/* or include=archive/*) and not (copies=archive:2 or copies=smallarchive:2 or (copies=archive:1 and copies=smallarchive:1))) or approxlackingcopies=1
groupwanted archive = (not (copies=archive:2 or copies=smallarchive:2 or (copies=archive:1 and copies=smallarchive:1)) or approxlackingcopies=1
One of the remotes is set as archive and two as smallarchive yet `sync
--content` only ever copies to one so as to satisfy `numcopies`. Is
this expected? Shouldn't it always try to make two copies in archive
or smallarchive?
Interestingly, it copies data to my `backup` also (which is an
extarnal drive, so always present). So it seems the prefered content
is only respected for clones and not special remotes. Is that true?
Do I have to run `git annex copy --to <archive-remote> --auto` to satisfy the content preferences?