diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-03 15:06:16 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-03 15:06:16 -0400 |
| commit | 519f4a60eac85bd3c2f56302e8265c08546ba523 (patch) | |
| tree | 726404b3adae55c468f18a9635248431fdc9d8c7 | |
| parent | bd804e4c15b8156da54aea4150021edf090f8ee3 (diff) | |
followup
| -rw-r--r-- | doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_2_50e35159f7e670ca6b7280121821b494._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_2_50e35159f7e670ca6b7280121821b494._comment b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_2_50e35159f7e670ca6b7280121821b494._comment new file mode 100644 index 000000000..40751e41f --- /dev/null +++ b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_2_50e35159f7e670ca6b7280121821b494._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2016-05-03T18:54:41Z" + content=""" +What you could try is: + + git config remote.s3.annex-gnupg-options --ignore-mdc-error + git config remote.s3.annex-verify false + +That should make gpg ignore the error and proceed, and make git-annex +not try to verify the download either. The resulting file will probably +be corrupt in some way. It might have a bad chunk in the middle, or be +truncated, or be garbage past a certian point. + +This sounds like something went wrong with the multipart upload to S3. +What does `git annex info s3` say about the configuration of your S3 +remote? I'd like to reproduce this problem, if possible. Since it hit two +of your files, it seems to not have been some kind of one-off data +corruption problem. +"""]] |