diff options
Diffstat (limited to 'doc/bugs/git-annex_merge_stalls')
| -rw-r--r-- | doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment new file mode 100644 index 000000000..600044354 --- /dev/null +++ b/doc/bugs/git-annex_merge_stalls/comment_3_ced9b0d724fb55c756106b64c3721003._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.255.110" + subject="comment 3" + date="2013-09-09T19:35:25Z" + content=""" +This problem cleared up after a reboot (and a crash, apparently). + +<pre> +joeyh so, my thought is that perhaps you had a git-annex process before that was holding the lock. +joeyh for example, if you ran it and ctrl-z'd at just the right time, it could be suspended and holding the lock +joeyh (or the kernel coud have gotten confused, which given you also had a crash, who knows..) +dp sounds logical +joeyh forcing locks is always a problimatic thing +joeyh but git-annex could certianly notice if it seems to be stalled and print some useful messages +joeyh and maybe have a way to run with locks forced +</pre> +"""]] |