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

comment

Browse source
This commit is contained in:
Joey Hess 2025-06-24 12:24:45 -04:00
parent efbadc2397
commit 064fdf531f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/forum/Fill_remotes_sequentially/comment_6_6f128a1a28298bb5662fa32e9b350946._comment Normal file
View file

@ -0,0 +1,24 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2025-06-24T16:13:56Z"
content="""
> It seems like that the remote's cost could be a way to define the order in which the remotes are filled?
Yes because git-annex always tries to use the lowest cost remote first when
storing or retrieving a file. So using eg the standard archive group
preferred content setting, it would store a file on the lowest cost remote,
and then the other remotes would no longer want a copy of the file since it
was already stored to one.
`GETCOST` defines the default cost for a special remote. So rather than
configuring `remote.<name>.annex-cost-command`, your special remote could
check if the expected tape is currently in the drive, and return a lower cost.
If the cost needs to change while git-annex is running, due eg to a tape
being swapped, it could re-query `GETCOST` after every file. Which would
be less expensive than running a cost command. I think that a config
setting to make it do that is a feasible change to make to git-annex.
(Ignore `GETAVAILABILITY`, it's barely used and only by the assistant.)
"""]]