bugs/Auto-repair greatly slows down the machinegit-annexhttp://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/git-annexikiwiki2014-06-10T19:31:38Zcomment 1http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_1_a52e4ef04209d0a2449165e2b4cb9ccc/joeyh.name2014-02-26T17:44:28Z2014-02-26T17:38:05Z
<p>Auto repair is not intended to be a common occurrance. It means something went badly, horribly wrong on your machine, and it lost data that git wrote to disk. It's more important in such a scenraio to get back to a working system eventually than to do something fast or inexpensively.</p>
<p>If you're seeing the need for auto repair on a weekly basis, your computer is failing in a horrible way horribly frequently, and the thing to do is to find out why, and fix that. Perhaps you need to start cleanly shutting down the system. Perhaps something is causing your computer to crash, and you need to fix that.</p>
comment 2http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_2_9f5340ab1012f335af0c246b82c1a777/EskildHustvedt2014-02-27T14:16:12Z2014-02-27T14:16:11Z
<p>That's the thing. The drive is fine, I've fscked it, and the machine is always shut down cleanly (and it is very stable, can't remember the last time it crashed). So there's no reason why this should be happening, and since git-annex doesn't say anything about why it started the auto-repair, I'm unable to track it down further.</p>
<p>It's also always this repository. I have several assistant managed repos on the same machine, and this is the only one that git-annex regulary starts repairing (and the only one that it has auto-repaired on another box as well). No files in the repository itself has ever been noticed as corrupt, nor has there been any indications anywhere else about problems, hardware or filesystem (nothing wrong in the 40 or so git repos on the machine, no problems with software installed on the drive, never seen anything in dmesg).</p>
<p>It's happening often enough for me to have to consider dropping use of the assistant. It could still be a problem with the machine (though it seems unlikely, given that it's consistently the same repo, and that it has done it with the same repo on other machines), but git-annex doesn't provide any information about it.</p>
<p>Could you add some more information about what it thinks is wrong to the logging?</p>
<p>Funnily enough, git-annex started repairing it again as I was writing this.</p>
comment 3http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_3_67bfccf0934075559d439b1deafc001e/Jan Ulrich2014-03-05T11:47:07Z2014-03-05T11:47:06Z
I observe something similar. Today git-annex started to repair a repository. CPU is at 100%, I can still work because I have a multikernel system, so I'll wait and see if it comes to an end.
comment 4http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_4_5fa785aa759d1a1917f2a292324fe5ec/Jan Ulrich2014-03-06T06:22:00Z2014-03-06T06:21:59Z
Just for the records. I just shutdown the daemon because it ran all night long with 100%.
comment 5http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_5_9fe529034ad0115792b58d7da99c167e/joeyh.name2014-03-06T18:14:37Z2014-03-06T18:14:37Z
auto-repair is only done if git fsck detects a problem. You can run git fsck yourself to see.
comment 6http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_6_93ed991ef2a74c18575073ca72e06185/Jan Ulrich2014-03-10T14:14:07Z2014-03-10T14:14:06Z
I manually ran git fsck without problems but git-annex still wants to repair something.
comment 7http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_7_4649fa11745ff668e43833209811d005/joeyh.name2014-05-21T18:31:54Z2014-05-21T18:31:54Z
<p>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.</p>
<p>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.</p>
comment 8http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_8_6138a48f0b7e8be2bb66430397afdf5a/EskildHustvedt2014-05-21T19:19:30Z2014-05-21T19:19:30Z
The trouble with providing more information (outside of the logfile above) is that by the time I realize that there is a problem it is because git-annex has started to repair. Perhaps an option that makes git-annex write a ~/.git/annex/repair-reason.log file with the reason (ie. git fsck output etc.) for starting the repair could help?
comment 9http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_9_3da5940bb2e9689b00239eec9a073f1c/EskildHustvedt2014-06-06T16:13:55Z2014-06-06T16:13:55Z
Any chance of any progress on this? Either a way to disable it, or some additional logging to track down the problem? git-annex is currently repairing one particular repository several times a month accross different machines, rendering git-annex practically unusable.
comment 10http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_10_d46c6314bff75a0ae679bc2358b28c2b/EskildHustvedt2014-06-07T05:47:25Z2014-06-07T05:47:25Z
Given that it's ususally the same repo, I'm going to try to create a completely fresh repository instead and see if the frequent auto-repairs are stopped by that.
comment 11http://git-annex.branchable.com/bugs/Auto-repair_greatly_slows_down_the_machine/comment_11_1c2c3adfbccd2b14a7d1c4618800e735/joeyh.name2014-06-10T19:31:38Z2014-06-10T19:31:38Z
Disable consistency checks for the repo in the webapp UI, wait until long enough that you're sure the assistant would be wanting to repair it again if you hadn't disabled that, and run <code>git annex repair</code> at the console so I can see what's going on.