clarify
authorJoey Hess <joeyh@joeyh.name>
Tue, 10 Nov 2015 18:49:34 +0000 (14:49 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 10 Nov 2015 18:49:34 +0000 (14:49 -0400)
doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_10_cdbd35ab0ba9c9157fd6530bebbc4650._comment [new file with mode: 0644]

diff --git a/doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_10_cdbd35ab0ba9c9157fd6530bebbc4650._comment b/doc/bugs/git-annex_doesn__39__t_work_on_lustre:_waitToSetLock:_unsupported_operation___40__Function_not_implemented__41__/comment_10_cdbd35ab0ba9c9157fd6530bebbc4650._comment
new file mode 100644 (file)
index 0000000..0b91fe8
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 10"""
+ date="2015-11-10T18:47:36Z"
+ content="""
+I think what yoh meant above was that -o lock (not `sync`) has a heavy
+performance impact. Or at least a perceived one. And thus, lustre clusters
+are not using it even though the feature is available and would probably be
+find for git-annex's use if enabled.
+"""]]