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

followup and retitle

Browse source
This commit is contained in:
Joey Hess 2015-02-04 15:34:45 -04:00
parent 470a6ec0d5
commit 7ab9f0b7d3
2 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -28,3 +28,5 @@ Clone a git annex repo on a network file system, run
# End of transcript or log. # End of transcript or log.
"""]] """]]
[[!meta title="git-annex and NFS don't mix; could git annex init detect NFS and refuse to use it?"]]

19
doc/bugs/huge_multiple_copies_of___39__.nfs__42____39___and___39__.panfs__42____39___being_created/comment_1_833cf2db9881a401a3d5db6d4f3c450a._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-02-04T19:31:32Z"
content="""
git-annex uses posix file locking to avoid scenarios that could
otherwise result in data loss when dropping a file.
This indeed involves keeping a file open and locked while removing it.
Since NFS's posix file locking support ranges from poor to completely
broken, it's not wise to use git-annex over NFS at all. It's much nicer
to use it locally, with a git remote accessing the file server over
eg, ssh.
I can't see any changes to git-annex that could improve its handing
of NFS, unless there's a good way to detect a NFS filesystem and make
`git annex init` refuse to set up a repository there.
"""]]