diff options
-rw-r--r-- | doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment b/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment new file mode 100644 index 000000000..34ed9f1d7 --- /dev/null +++ b/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-06-09T17:25:23Z" + content=""" +I have not had any luck with reproducing the problem, using +your script, on Debian unstable. The transfer repo gets +the file contents and both it and the source repo knows where they are. + +Do you see the same behavior if, rather than running the assistant +for 30 seconds, you run `git annex sync --content` ? + +Are you using git-annex in direct mode and/or on an unusual filesystem? +"""]] |