summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar openmedi <openmedi@web>2016-08-17 14:15:53 +0000
committerGravatar admin <admin@branchable.com>2016-08-17 14:15:53 +0000
commit54ef473c76f728bd898b592ea1b8ce78369c84bf (patch)
tree46b4a9acb2bd78a1e51e77fef6ee1f0bf7eec548
parentd9c62934ff1d0b9f168f48d9e7476857eea23ac6 (diff)
-rw-r--r--doc/forum/how_to_disaster_recovery.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/forum/how_to_disaster_recovery.mdwn b/doc/forum/how_to_disaster_recovery.mdwn
new file mode 100644
index 000000000..b4bbe123d
--- /dev/null
+++ b/doc/forum/how_to_disaster_recovery.mdwn
@@ -0,0 +1,6 @@
+OS X: 10.11.6
+Annex: git-annex-6.20160619 (via brew)
+
+I'm [still strugling](http://git-annex.branchable.com/forum/git_annex_wants_to_repair_every_time_it__39__s_running/) with my annex repo over here. My problem is that for some reason git annex wants to repair my repo all the time when I'm starting the assistant and this (seemingly) never finishes, so I'm caught in an infinite loop in which no files get uploaded to my various remotes and nothing is downloaded either leaving me with all the data on my hard drive and nothing else. I would like to move on. How can I recover from this state? The daemon.log file doesn't show any information about what is happening during the repair and what might cause the failure. Is there another log file I could look at?
+
+Any help is appreciated at that point. Where should I look for more information? What should I do to change the behaviour? I want to solve this once and for all.