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

merge

Browse source
This commit is contained in:
Joey Hess 2020-03-02 16:08:31 -04:00
parent be8589d5e9
commit 41a5c47860
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/bugs/drop_on_NFS___40__no_pidlock_need_detected__41___leaves_annex__47__objects__47__XX__47__YY__47__KEY_dir_behind_.mdwn
View file

@ -192,3 +192,7 @@ drop file1 ok
[[!meta author=yoh]]
[[!tag projects/datalad]]
> merged with
> <https://git-annex.branchable.com/bugs/huge_multiple_copies_of___39__.nfs__42____39___and___39__.panfs__42____39___being_created/>
> [[done]] --[[Joey]]

13
doc/bugs/drop_on_NFS___40__no_pidlock_need_detected__41___leaves_annex__47__objects__47__XX__47__YY__47__KEY_dir_behind_/comment_3_6c79c41676318bd976eff9988463d167._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2020-03-02T19:56:49Z"
content="""
Sure, some minor change in git-annex could tickle non-deterministic
behavior, eg something to do with timing of when it deletes the file
vs the later closing of the file that drops the lock.
That regression made git-annex init fail when NFS doesn't have posix lock
support enabled. It can detect that, and enables pidlock, but it can't
detect NFS when it is pretending to support posix locks.
"""]]

2
doc/bugs/huge_multiple_copies_of___39__.nfs__42____39___and___39__.panfs__42____39___being_created.mdwn
View file

@ -30,3 +30,5 @@ Clone a git annex repo on a network file system, run
"""]]
[[!meta title="git-annex and NFS don't mix; could git annex init detect NFS and refuse to use it?"]]
[[!tag projects/datalad]]