From 7ba7ec49beefa4557e5bdd2078671e86f6388b62 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmnG4EuvZWse5hvgrl0XAK-U61e-0iGaao" Date: Mon, 1 Oct 2012 20:31:19 +0000 Subject: [PATCH] Added a comment: nolock option worked --- .../comment_4_e42146d2dcc4052266dd61d204aeb551._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment diff --git a/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment new file mode 100644 index 0000000000..59919789e9 --- /dev/null +++ b/doc/bugs/Trouble_initializing_git_annex_on_NFS/comment_4_e42146d2dcc4052266dd61d204aeb551._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmnG4EuvZWse5hvgrl0XAK-U61e-0iGaao" + nickname="David" + subject="nolock option worked" + date="2012-10-01T20:31:18Z" + content=""" +I had the same problem on my NAS, updated the firmware but it didn't solve it. The remedy was to mount the NAS with the 'nolock' option. +"""]]