From c093839a40034a6e3fa967a18459a52ea326b867 Mon Sep 17 00:00:00 2001
From: "http://cgray.myopenid.com/" <cgray@web>
Date: Tue, 15 Nov 2011 00:41:08 +0000
Subject:

---
 doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn

(limited to 'doc')

diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn b/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn
new file mode 100644
index 000000000..23977af34
--- /dev/null
+++ b/doc/bugs/Trouble_initializing_git_annex_on_NFS.mdwn
@@ -0,0 +1,14 @@
+The following occurs in a directory that is shared on an NFS server:
+
+    /media/mybook/movies $ git init
+    Initialized empty Git repository in /media/mybook/movies/.git/
+    /media/mybook/movies $ git annex init mybook-movies
+    init mybook-movies 
+    git-annex: waitToSetLock: resource exhausted (No locks available)
+    failed
+    git-annex: init: 1 failed
+    /media/mybook/movies $
+
+This happens reliably.  Is there any way around it?  I have shell
+access on the NFS server, but it is a NAS, so I don't think it is
+capable of running git-annex.
-- 
cgit v1.2.3