summaryrefslogtreecommitdiff
path: root/doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawk9nck8WX8-ADF3Fdh5vFo4Qrw1I_bJcR8 <Jon_Ander@web>2014-12-16 10:19:39 +0000
committerGravatar admin <admin@branchable.com>2014-12-16 10:19:39 +0000
commit9ded4689de6c2d77819265170ac3d814aa06802f (patch)
tree4900bcce1ad3ee2e7bedd87509448982b20d919c /doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn
parentac7477246d1ae329a31f5b6cbdd140a11ecf85a6 (diff)
Diffstat (limited to 'doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn')
-rw-r--r--doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn b/doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn
new file mode 100644
index 000000000..6925606f0
--- /dev/null
+++ b/doc/bugs/Attempting_to_repair_repository_almost_every_day.mdwn
@@ -0,0 +1,5 @@
+I'm using the webapp on my two main computers with up-to-date Debian (one has testing and the other one sid) and I have consistency checks scheduled every day.
+
+The problem is that almost every time the check runs I'm getting the "Attempting to repair" message and git-annex starts using 100% CPU for quite a while, but after it it seams to have done no change to the git tree or the files.
+
+The two computers are never on at the same time, but they are constantly syncing files (through box.com), I don't now if downloading files while the check is in progress might have something to do.