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

analysis of deadlock

Browse source
This commit is contained in:
Joey Hess 2020-06-18 12:10:54 -04:00
parent 0f43efa15b
commit 348821c9cf
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/bugs/one_annex_test_FAILs_when_HOME_is_a_crippled_fs/comment_11_1147b988f7b770b4ce4d077bb10a9760._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 11"""
date="2020-06-18T15:52:10Z"
content="""
git-annex smudge is locking the git queue in order to run
restagePointerFile.
And of course, restagePointerFile has run git update-index, which has run
git-annex smudge.
Normally git-annex smudge avoids this loop. In this case,
Database.Keys.reconcileStaged is what calls restagePointerFile
(for reasons explained in [[!commit 50fa17aee64ae778eb071cc21d5be85ce969bd9b]]).
So, there needs to be something to prevent restagePointerFile from running
in git-annex smudge, no matter how it's called.
Also, I suspect that vfat's timestamp granularity is exposing the problem.
On other filesystems, I don't see git-annex smudge calling restagePointerFile.
"""]]