diff options
author | 2016-09-05 12:49:13 -0400 | |
---|---|---|
committer | 2016-09-05 12:49:13 -0400 | |
commit | 6296381524a9c58c9a51e92ee4f8bf083ffec9ca (patch) | |
tree | 264d07b07e7e03b9502273b00f8f3c9add6cb3d7 | |
parent | 9b9b4d42bcf89a4c1860380547518ce761514831 (diff) |
comment
-rw-r--r-- | doc/todo/Specify_maximum_usable_space_per_remote/comment_1_fdc0c518b6cbc5dc7e5b64748c2d7b01._comment | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/todo/Specify_maximum_usable_space_per_remote/comment_1_fdc0c518b6cbc5dc7e5b64748c2d7b01._comment b/doc/todo/Specify_maximum_usable_space_per_remote/comment_1_fdc0c518b6cbc5dc7e5b64748c2d7b01._comment new file mode 100644 index 000000000..1365e932c --- /dev/null +++ b/doc/todo/Specify_maximum_usable_space_per_remote/comment_1_fdc0c518b6cbc5dc7e5b64748c2d7b01._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-09-05T16:40:56Z" + content=""" +This poses difficulties when several different git-annex repositories +are uploading to the same special remote. They would have to somehow maintain a +count of the amount of space used on the remote, but the repositories +could be completely disconnected, other than being able to all access the +special remote. So, the count would have to be stored on the remote, and +updated atomically. But, not all remotes support atomic operations well +enough to support such a distributed counter. + +If the storage service has an API call to get the space used, then the +special remote can use that. I think that such a thing unfortunately can +only be implemented that way, on a per-special-remote implementation basis. +"""]] |