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

Merge branch 'master' into requirednumcopies

Browse source
This commit is contained in:
Joey Hess 2021-01-06 14:24:09 -04:00
commit 4694c2bb87
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 2 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/todo/lockContent_for_special_remotes.mdwn
View file

@ -1,6 +1,6 @@
Support lockContent in more special remotes. This allows dropping Support lockContent in more special remotes. This allows dropping
content from a special remote when the only copies are in other special content from a special remote when the only copies are in other special
remotes. remotes, without needing to set mincopies to 0 and risk losing content.
(All the easy ones, eg read-only special remotes, are implemented already.) (All the easy ones, eg read-only special remotes, are implemented already.)
@ -12,7 +12,7 @@ remotes.
If this were implemented in git-annex, and some special remote program If this were implemented in git-annex, and some special remote program
didn't used to support it, and implemented REMOVE w/o checking a lock, didn't used to support it, and implemented REMOVE w/o checking a lock,
then making that program support lockContent would run the risk then making that program support lockContent would run the risk
of a misture of the old and new version being in use for the same remote, of a mixture of the old and new version being in use for the same remote,
which could result in data loss. which could result in data loss.
To avoid that, the author of the special remote would need to either To avoid that, the author of the special remote would need to either
@ -46,16 +46,3 @@ remotes.
* adb could use some shell trick perhaps.. But it would depend on doing * adb could use some shell trick perhaps.. But it would depend on doing
locking in /sdcard, which seems likely to be a massive ball of POSIX locking in /sdcard, which seems likely to be a massive ball of POSIX
incompliance and pain. incompliance and pain.
----
I was thinking about something related to this recently. Dropping currently
guaranteeds numcopies will be maintained for remotes that support
lockContent. But when some of the copies are on special remotes, this
is not guaranteed. It only makes sure lockContent is keeping one copy
locked, and can verify the existence of the other copies less stringently.
So perhaps it would be good to make this explicit in the configuration,
by adding a mincopies. (Analagous to required content configs.)
Defaulting to 1 as now, but if the user wants to they can set it higher,
perhaps as high as their numcopies, or higher.