bugs/TransferScanner crashed: fd:59: hGetLine: end of filegit-annexhttp://git-annex.branchable.com/bugs/TransferScanner_crashed__58___fd__58__59__58___hGetLine__58___end_of_file/git-annexikiwiki2016-03-12T16:58:09Zcomment 1http://git-annex.branchable.com/bugs/TransferScanner_crashed__58___fd__58__59__58___hGetLine__58___end_of_file/comment_1_a1392b92efdff82783a4b0cc2c3c7f2f/joeyh.name2016-03-12T16:58:09Z2014-07-14T18:47:21Z
<p>You did not seem to paste the whole log, but it's clear that your git repository is corrupt. You might try running <code>git annex repair</code> inside it.</p>
<p>This was probably caused by a disk corruption or if you're lucky just a hard shutdown that caused files to get truncated.</p>
<p>The assistant tries to detect corrupt repositories on startup, but it's hard to detect when a repository has a few corrupt objects like this. This is why the webapp suggests you set up periodic repository consistency checks, which should eventually repair this kind of problem.</p>
<p>Perhaps it would make sense for the webapp, when a thread crashes, to provide a button to run an consistency check immediately.</p>
comment 2http://git-annex.branchable.com/bugs/TransferScanner_crashed__58___fd__58__59__58___hGetLine__58___end_of_file/comment_2_5e153b7c59c474988fe551a505e545bc/jg123h12jh3y12g3y2016-03-12T16:58:09Z2014-07-15T07:58:15Z
But I do have periodice consistency checks turned on. I think git-annex assistant should tell the user what the heck is going on and maybe try to repair it automatically.