From a3e19cef167d09220b8d048cc47b9dff186019e2 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 21 May 2014 18:31:54 +0000 Subject: Added a comment --- .../comment_7_4649fa11745ff668e43833209811d005._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_7_4649fa11745ff668e43833209811d005._comment diff --git a/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_7_4649fa11745ff668e43833209811d005._comment b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_7_4649fa11745ff668e43833209811d005._comment new file mode 100644 index 000000000..58499da8b --- /dev/null +++ b/doc/bugs/Auto-repair_greatly_slows_down_the_machine/comment_7_4649fa11745ff668e43833209811d005._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.3" + subject="comment 7" + date="2014-05-21T18:31:54Z" + content=""" +It seems to me that if you don't want to repair your repository, you can just go into the webapp and disable all scheduled consistency check jobs. + +If someone with this problem would like to run \"git annex repair\" at the console, and paste the output, perhaps I could then see why it thinks it needs to repair the repository. So far, I have nothing to go on, and no proof that this is a bug at all, and not just people with actually corrupted repositories that really do need to be repaired. +"""]] -- cgit v1.2.3