summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar jonan <jonan@web>2016-10-25 10:51:29 +0000
committerGravatar admin <admin@branchable.com>2016-10-25 10:51:29 +0000
commit2223c3f66b2c6148d59ea0a19f4bb2af6c1dda24 (patch)
tree2886385711273ebfe32045eb4d4b24f7113df914
parent68dabbfc4ad2a6c430b74707724b96311529b249 (diff)
-rw-r--r--doc/bugs/Files_reappear_after_delete.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/bugs/Files_reappear_after_delete.mdwn b/doc/bugs/Files_reappear_after_delete.mdwn
new file mode 100644
index 000000000..f53963945
--- /dev/null
+++ b/doc/bugs/Files_reappear_after_delete.mdwn
@@ -0,0 +1,25 @@
+### Please describe the problem.
+I normally use two clients with the assistant (lets call them A and B) and they are usually online at different times.
+Sometimes, after deleting a file in A, I turn on the client in B and when rescanning, instead of deleting that same file from B, it adds it back to A.
+
+I can always delete the file again, but it's a bit annoying. Anyway, it's a lot better than data loss ;)
+
+Might be worthy to mention that the computer running client B is quite slow and has a slow HD. I have 4 git-annex repositories and when I turn on the computer the rescan can easily take up a couple of hours.
+
+
+### What steps will reproduce the problem?
+B -> is turned off
+
+A -> delete file
+
+B -> turn on and wait for rescan
+
+B -> readds the file instead of deleting it
+
+
+### What version of git-annex are you using? On what operating system?
+6.20160923 (Debian Sid)
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+
+I've been using git-annex for years with 4 different repositories, 3 of them pretty big (> 50 GB) and I'm really happy! :)