devblog/day 321 download verificationgit-annexhttp://git-annex.branchable.com/devblog/day_321__download_verification/git-annexikiwiki2015-10-04T23:33:52Zcomment 1http://git-annex.branchable.com/devblog/day_321__download_verification/comment_1_424367fba4db56f4699952572bd3d605/spwhitton2015-10-02T04:13:07Z2015-10-02T04:13:07Z
It might be nice to set <code>annex.verify-threshold</code> to verify all files below a certain size. This could default to 500MB.
comment 2http://git-annex.branchable.com/devblog/day_321__download_verification/comment_2_926cc165e99f2e125c909bd706460a05/spwhitton2015-10-02T04:15:48Z2015-10-02T04:15:48Z
I mean: <em>only</em> files below that size.
comment 3http://git-annex.branchable.com/devblog/day_321__download_verification/comment_3_fb0ed50c27a493c3494bf2efbf9a9c5d/encryptio2015-10-03T21:09:31Z2015-10-03T21:09:31Z
Nice! I actually had been doing <code>git annex get $file && git annex fsck $file</code> in all my scripts already because I had run into an issue where a bad file got replicated everywhere, and the only good copy I had was <code>drop</code>ped before I realized. This would have caught it. Thanks!
Yay, man!http://git-annex.branchable.com/devblog/day_321__download_verification/comment_4_fecb2d6349aa61f1c76525178fea4598/sunny2562015-10-04T23:33:52Z2015-10-04T23:28:43Z
I love this! Especially since I've noticed some read errors on my laptop disk now and then. Not when using git-annex, I've never lost a file with it, but when doing other things. I've been hoping for this, as I've used computers with memory corruption years ago, and in cases like that, all bets are off and you'll only hope that the file copy goes well. I've grown quite paranoid after that computer, and have enabled everything in git (setting <code>fetch.fsckObjects</code>, <code>receive.fsckObjects</code> and <code>transfer.fsckObjects</code> to <code>true</code>) to catch potential errors as a result of bad disk, memory corruption or transfer errors over the network. I'd rather wait a bit longer while copying or especially moving files than wait for that single corrupted bit in the only copy of a 4 gig file. Thanks!