From: Joey Hess <joeyh@joeyh.name>
Date: Mon, 30 Nov 2015 19:50:55 +0000 (-0400)
Subject: um
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~322^2~44
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=906cf4ea2786eee55959f1c0ca5a3cef1d8d4107;p=git-annex.git

um
---

diff --git a/doc/bugs/Unable_to_take_transfer_lock/comment_1_4eff7f261659202084d32e068b93f77b._comment b/doc/bugs/Unable_to_take_transfer_lock/comment_1_4eff7f261659202084d32e068b93f77b._comment
new file mode 100644
index 0000000000..3db482bc19
--- /dev/null
+++ b/doc/bugs/Unable_to_take_transfer_lock/comment_1_4eff7f261659202084d32e068b93f77b._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-11-30T19:46:05Z"
+ content="""
+The most likely reason for that error message would be if a transfer
+of the same file was already in progress by another git-annex process.
+
+It might also be the case that if you're trying to access a git-annex
+repository via SMB, the POSIX fcntl locking that git-annex needs to do
+don't work. This is often the case with various network filesystems.
+Solution is to make the url for the git remote be a ssh:// url instead.
+
+I don't know what OSX's case-insensative complication could have to do with
+this, although it certianly seems to be a good way to get completely
+unexpected behavior.
+
+Is there an actual bug here? What are the steps to reproduce
+it?
+"""]]