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

exclusive locks, ugh

Browse source
This commit is contained in:
Joey Hess 2011-11-09 22:15:33 -04:00
parent cf0174c922
commit a218ce41cf
2 changed files with 19 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

9
doc/bugs/cyclic_drop.mdwn
View file

@ -73,6 +73,15 @@ Another cycle might be running move --to and move --from on the same file,
locally. The exclusivity of the content lock solves this, as only one can
run at a time.
Would it work with a shared lock? The --to would run git-annex-shell
inannex. The --from would also be running, and would run git-annex-shell
dropkey. So inannex and dropkey would end up running on the remote
at the same time. Dropkey takes the content lock, and inannex checks it,
but what if inannex runs first? Then it returns true, and then the content
is removed, so both the --to and --from see success and the --to proceeds
to remove the local content that the --from already caused to be removed
from the remote. So, no, the nasty exclusive lock is needed.
---
Another cycle might involve move --from and drop, both run on the same